BaseX-Talk

basex-talk@mailman.uni-konstanz.de

4 participants
5268 discussions

jobs:list-details o/p
by Andy Bunce 13 Feb '19

13 Feb '19

Hi, Before BaseX 9 jobs:list-details would return the query string used in the jobs:eval (or the uri if that was used) - as per the current docs [1] Versions 9+ returns a "dummy" file name in this case. jobs:eval("2+4",(),map{"cache":true()}) jobs:list-details("job2") <job id="job2" type="QueryJob" state="cached" user="admin" duration="PT0.001S" reads="(none)" writes="(none)" time="2019-02-12T17:53:41.772Z">file:///C:/Users/andy/git/vue-poc/src/vue-poc/features/tasks/model.build/file</job> I found the old behavior useful, (although it missed recording the static-base-uri). /Andy [1] http://docs.basex.org/wiki/Jobs_Module#jobs:list-details

2 2

starts-with in a satisfies statement fails to fail
by George Sofianos 13 Feb '19

13 Feb '19

Hi, I have a specific piece of code which fails to run as expected. Unfortunately i didn't manage to create an MCVE so far. The part of code that should fail in my script is: some $i in $data satisfies starts-with($i, $string) Where $data is a list of strings, and $string is a sequence of two strings - example ("S1", "S2"). The Query executes without error, but the trace message is never visible. The part of the Query plan that executes successfully (while it shouldn't) is: <StaticFunc name="common:startsWith" type="xs:boolean" arg0="elements" arg1="string"> <GFLWOR type="xs:boolean" size="1"> <Let type="xs:string*"> <Var name="$string" id="178" type="xs:string*"/> <FnTrace name="trace(value[,label])" type="xs:string*"> <StaticFuncCall name="common:string" tailCall="false" type="xs:string*"> <VarRef> <Var name="$string" id="177" type="item()*" promote="true"/> </VarRef> </StaticFuncCall> <Str type="xs:string">STRING: </Str> </FnTrace> </Let> <Quantifier option="some" type="xs:boolean" size="1"> <GFLWOR type="xs:boolean*"> <For type="xs:string" size="1"> <Var name="$i" id="180" type="xs:string"/> <StaticFuncCall name="common:string" tailCall="false" type="xs:string*"> <VarRef> <Var name="$elements" id="176" type="item()*" promote="true"/> </VarRef> </StaticFuncCall> </For> <FnTrace name="trace(value[,label])" type="xs:boolean" size="1"> <FnStartsWith name="starts-with(string,sub[,collation])" type="xs:boolean" size="1"> <VarRef type="xs:string" size="1"> <Var name="$i" id="180" type="xs:string"/> </VarRef> <VarRef type="xs:string*"> <Var name="$string" id="178" type="xs:string*"/> </VarRef> </FnStartsWith> <Str type="xs:string">SATISFY: </Str> </FnTrace> </GFLWOR> </Quantifier> </GFLWOR> </StaticFunc> I'm not sure if you can find anything from the Query plan for why this is happening. This fails either with or without inlining. Regards, George

2 4

Version
by Bondeson, Carl 11 Feb '19

11 Feb '19

Is there a method in a Java client/server architecture to get the current version of BaseX (i.e. 9.1.2)? I could not find it anywhere. ClientSession.info is always blank. Thanks Carl R Bondeson IT Analyst 3 Department of Public Health Operation & Support Services Information Technology Phone: 860-509-7434 Carl.Bondeson(a)ct.gov<mailto:Carl.Bondeson@ct.gov> [cid:image001.jpg@01D16B2F.0AD71DC0][http://www.phaboard.org/wp-content/uploads/PHAB-SEAL-COLOR.jpg]

2 7

Database currupted bug when trying to re-insert documents
by Herbert Mertig 11 Feb '19

11 Feb '19

I stumbled over this while running some JUnit tests of our Applications which uses the embedded version of BaseX. It always seemed to happen when inserting, deleting and then inserting the same documents again. I attached 4 simple xquery files to reproduce it using basexgui, just follow these steps: 1. open basexgui 2. create an empty database 3. run insert_pigs.xq to insert the first document 4. run insert_plants.xq to insert the second document 5. run delete_pigs.xq to delete the first document 6. run delete_plants.xq to delete the second document now insert the same 2 documents in the opposite order 7: run insert_pigs.xq 8. run insert_plants.xq <-- this will trigger the error, the database is now garbage Some more observations: It does not trigger when using only 1 document. Not sure if it happens with more than 2, I think I have observed that as well. Sometimes closing the database and running optimize on it seems to fix it. Hope that helps to find and fiy the bug, its pretty nasty. BR Herbert

2 9

Global locks
by Andy Bunce 11 Feb '19

11 Feb '19

Running the following in the GUI (8.6.5) ``` let $db:="BEP" return count(collection($db)) ``` The info windows shows $db is inlined Compiling: - inline $db_0 - pre-evaluate collection("BEP") to document-node() sequence - pre-evaluate count((db:open-pre("BEP",0), ...)) to xs:integer - simplify gflwor Optimized Query: 9193 All good. Submitting a job ``` let $q:='let $db:="BEP" return count(collection($db))' return jobs:eval($q,(),map{"cache":true()})!(jobs:wait(.),jobs:list-details(.)) ``` returns: <job id="job90" type="ScheduledXQuery" state="cached" user="admin" duration="PT0.007S" reads="(global)" writes="(none)">let $db:="BEP" return count(collection($db))</job> Note @reads="(global)" But ``` let $q:='count(collection("BEP"))' return jobs:eval($q,(),map{"cache":true()})!(jobs:wait(.),jobs:list-details(.)) ``` <job id="job92" type="ScheduledXQuery" state="cached" user="admin" duration="PT0.006S" reads="BEP" writes="(none)">count(collection("BEP"))</job> Note @reads="BEP" Is this correct and/or of any consequence? /Andy

2 8

Global lock = false and parallel update processes to different DBs
by France Baril 06 Feb '19

06 Feb '19

Hi! I noticed that the latest version of BaseX lost this feature and nothing seems to replace it. I'm trying to improve performance of batch processes and I was counting on that feature a lot. Any change it will come back or that something equivalent will come? Case: .js: For $lang in $langs call basex updating function: . xqm updating function: get db:open($lang)/* process save to db:open('staging-' || $lang) This is a case where there is no chance of conflict because each thread saves to a different db. Any suggestion on how to apply parallel processing for this case is welcome. -- France Baril Architecte documentaire / Documentation architect france.baril(a)architextus.com

3 5

WWW-Authenticate header
by Johannes Bauer 05 Feb '19

05 Feb '19

Hello BaseX Team, I'm trying to implement a RESTXQ service that uses JWT tokens for authorization and authentication. For this purpose I use a permission check annotated function that validates the token and returns a 401 response if the token is invalid or missing. declare %perm:check('/admin','{$perm}')function security:check-admin($perm) { let $token := $perm?authorization where empty($token) return <rest:response> <http:response status='401'> <http:header name='WWW-Authenticate' value='Bearer realm="c42"'/> </http:response> </rest:response> }; When I call the endpoint without token I get the expected response but the WWW-Authenticate header is different to the one that I have defined: WWW-Authenticate Basic realm="BaseX" Is there a way to override the BaseX provided header? Thanks for your input. Best regards Johannes

2 2

%perm:allow annotation
by Johannes Bauer 04 Feb '19

04 Feb '19

Hi again, I've another question about the %perm:allow annotation. Is it possible to use multiple instances of this annotation? My expectation would be that any of the listed roles is allowed to call the function. For example: declare %rest:GET %rest:path("/multi") %perm:allow("role1") %perm:allow("role2") function test:multi()as item()* { <response>multi</response> }; declare %rest:GET %rest:path("/single") %perm:allow("role1") function test:single()as item()* { <response>single</response> }; declare %perm:check('/admin','{$perm}')function test:check($perm) { () }; When I call /multi the first time I get a response. But all further calls to /multi will result in a NullPointerException. Calls to /single do not have this problem. My error stacktrace is: java.lang.NullPointerException at org.basex.util.list.ObjectList.finish(ObjectList.java:235) at org.basex.query.value.seq.StrSeq.get(StrSeq.java:64) at org.basex.http.restxq.RestXqPerm.map(RestXqPerm.java:43) at org.basex.http.restxq.RestXqFunction.bind(RestXqFunction.java:263) at org.basex.http.restxq.RestXqResponse.bind(RestXqResponse.java:61) at org.basex.http.web.WebResponse.create(WebResponse.java:53) at org.basex.http.restxq.RestXqServlet.run(RestXqServlet.java:50) at org.basex.http.BaseXServlet.service(BaseXServlet.java:59) at javax.servlet.http.HttpServlet.service(HttpServlet.java:742) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:231) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:166) at org.apache.tomcat.websocket.server.WsFilter.doFilter(WsFilter.java:52) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:193) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:166) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:199) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:96) at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:478) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:140) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:81) at org.apache.catalina.valves.AbstractAccessLogValve.invoke(AbstractAccessLogValve.java:650) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:87) at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:342) at org.apache.coyote.http11.Http11Processor.service(Http11Processor.java:803) at org.apache.coyote.AbstractProcessorLight.process(AbstractProcessorLight.java:66) at org.apache.coyote.AbstractProtocol$ConnectionHandler.process(AbstractProtocol.java:868) at org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.doRun(NioEndpoint.java:1459) at org.apache.tomcat.util.net.SocketProcessorBase.run(SocketProcessorBase.java:49) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) at org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:61) at java.lang.Thread.run(Thread.java:745) I think the error is at the location where he parses the perm:allow annotations. Best regards Johannes

2 1

BaseX-specific serialization parameters
by Joe Wicentowski 31 Jan '19

31 Jan '19

Hi all, As I read the serialization spec ( https://www.w3.org/TR/xslt-xquery-serialization-31/#serparam), additional values for the "method" parameter and additional serialization parameters should use a non-null namespace URI (see quotes below). I believe BaseX's "csv" method or "tabulator" parameter ( http://docs.basex.org/wiki/Serialization) would fall into this category. Without such a non-null namespace URI, users may mistake BaseX-specific serialization features for those supported in the spec. The solution that the spec seems to suggest would be to use "basex:csv" or "basex:tabulator". I bet such a change would be unwelcome to those with code that uses the existing supported values, but aside from a disruptive cycle of deprecating existing values, etc., an alternative would be for the BaseX documentation to note this non-compliance with the spec. I realize this is nit-picky, but I thought it might be worth raising given the potential for confusion mentioned above, and should this discussion be of interest to anyone. Best, Joe Regarding values for the "method" parameter: > The value of the method parameter is an expanded QName. If the value has a null namespace URI, then the local name identifies a method specified in this document and MUST be one of xml, html, xhtml, text, json , or adaptive; in this case, the output method specified MUST be used for serializing. If the namespace URI is non-null, then it identifies an implementation-defined output method; the behavior in this case is not specified by this document. Regarding additional serialization parameters: > Implementations MAY define additional serialization parameters, and MAY allow users to do so. For this purpose, the name of a serialization parameter is considered to be a QName; the parameters listed above are QNames whose expanded-QName has a null namespace URI, while any additional serialization parameters that are either implementation-defined or defined by the host language MUST have names that are namespace-qualified.

2 2

ubuntu 18.04 (bionic)
by Ветошкин Владимир 31 Jan '19

31 Jan '19

2 2

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

BaseX-Talk