BaseX-Talk

basex-talk@mailman.uni-konstanz.de

6 participants
5269 discussions

BaseX stop scripts
by Thomas Daly 11 May '17

11 May '17

Hello, a) I don't see the point of the 'basexserverstop' and 'basexhttpstop' scripts. If I run the server as a foreground process, the only way of stopping it (that I'm aware of) is to press CTRL-C, in which case there is no opportunity to run 'basexserverstop'. If I run the server as a background process, how will the 'basexserverstop' script know which process ID to kill? b) Please can I have a login for the documentation wiki? I think I tried applying through the site, but didn't receive a response. Best regards, Thomas

2 2

File name changed
by celano＠informatik.uni-leipzig.de 11 May '17

11 May '17

Hi All, It is not clear to me why, when I tried to save the result of one query in a file called 6-2.xml, BaseX automatically converted this name into 4.xml. Similar name changes happened with files I wanted to name 1-2.xml and 10-2.xml. I attach part of the query info output (with highlights for the relevant points) Query: declare variable $pp := doc("/cluster/home/g/files/all.xml")/d/t; for $s at $c in collection("/cluster/home/g/files/splitted-db/")[6] return file:write("/cluster/home/g/results2/" || 6-2 || ".xml", <sub-db>{ for $e in $s//d let $db := $pp[$e/p = ./p and $e/f = ./f] return if ($db) then element d {$e/@*, $e/*, for $u in $db/l return element e {$u/text()}} else $e }</sub-db> ) Compiling: - pre-evaluating doc("/cluster/home/g/files/all.xml") - pre-evaluating collection("/cluster/home/g/files/splitted-db/") - rewriting ((db:open-pre("splitted-db",0), ...))[position() = 6] - type check removed: $c_2 as xs:integer - pre-evaluating (6 - 2) - pre-evaluating concat("/cluster/home/g/results2/", 4, ".xml") - rewriting descendant-or-self step(s) - swapping operands: (p = $e_3/*:p) - swapping operands: (f = $e_3/*:f) - rewriting ((p = $e_3/*:p) and (f = $e_3/*:f)) to predicate(s) - pre-evaluating boolean((p = $e_3/*:p)) - pre-evaluating boolean((f = $e_3/*:f)) - rewriting singleton for to let - inlining $s_1 - converting descendant::*:d to child steps - inlining $c_2 - simplifying flwor expression Best, Giuseppe

2 2

Re: [basex-talk] Java Modules - Constructor
by Andy Bunce 08 May '17

08 May '17

Hi Ilko, >The repo folder was completely empty. So you want to install it in the repository, using repo install? My test was installing via copying the jar to basex/lib/ where it works (for me). If I use repo install I get the same problem as you. This may be a bug/feature. It is possible that using the full EXPath Packaging [1] xar would work although I have not tried it. This would involve adding an XQuery file with expath-pkg.xml and basex.xml files to create a xar wrapping the jar, structured as here [2] The issue [3] may be relevant. Regards /Andy hello-test.jar <https://drive.google.com/file/d/0B_HWsgek7hAeTjFnSFg3cGVpMXc/view?usp=drive…> [1] http://docs.basex.org/wiki/Repository#Java_2 [2] https://github.com/expkg-zone58/metadata-extract/tree/master/src/main [3] https://github.com/BaseXdb/basex/issues/1413 On 8 May 2017 at 11:44, kovacic <kovacic(a)dke.uni-linz.ac.at> wrote: > Hi Andy, > > I have removed all other existing modules before installing this module. > The repo folder was completely empty. > > Regards > Ilko > > Am 05.05.2017 um 19:29 schrieb Andy Bunce: > > Hi IIko > > Your code and: > > declare namespace t='org.basex.modules.Hello'; > let $obj := t:new('works for me') > return t:hello($obj) > > Returns: > > Hello works for me > > Could be be that you have multiple versions of the jar on the path? > > Regards > /Andy > > On 5 May 2017 at 11:20, kovacic <kovacic(a)dke.uni-linz.ac.at> wrote: > >> Hi all, >> >> I am running BaseX 8.6.3 currently and struggling with the inclusion of >> modules written in Java. I have extended the Hello World example: >> >> package org.basex.modules; >> >> public class Hello { >> >> private String str = "BaseX"; >> >> public Hello() {} >> >> public Hello(String str) { >> this.str = str; >> } >> >> public String hello(final String world) { >> return "Hello " + world; >> } >> >> public String hello() { >> return "Hello " + str; >> } >> } >> >> I can pack it into a jar-file and install it successfully. My jar-file is >> structured as following: >> >> hello.jar >> - META-INF >> - MANIFEST.MF >> - org >> - basex >> - modules >> - Hello.class >> >> Here is the content of my manifest.mf: >> >> Manifest-Version: 1.0 >> Main-Class: org.basex.modules.Hello >> >> The methods of the Hello-class can be called without any problems when >> the module is imported: >> >> import module namespace t='org.basex.modules.Hello'; >> >> t:hello('text') >> >> However, when I try to explicitly create the object by calling the >> constructor (new) with arguments it fails: >> >> declare namespace t='org.basex.modules.Hello'; >> >> let $obj := t:new('test') >> >> return '' >> >> When I try to call the constructor I receive the error [XPST0017] Unknown >> function: Q{org.basex.modules.Hello}new. >> >> Since I am able to execute the FileWriter example ( >> http://docs.basex.org/wiki/Java_Bindings#Namespace_Declarations) which >> calls a constructor with an argument I would like to know if this behavior >> is a bug or if I am missing an important point. >> >> Regards, >> Ilko >> >> >> > > -- > *Ilko Kovacic* > Wissenschaftlicher Mitarbeiter > Institut für Wirtschaftsinformatik - Data & Knowledge Engineering > > > *JOHANNES KEPLER UNIVERSITÄT LINZ* > Altenberger Straße 69 > Science Park III, S3 111 > 4040 Linz, Österreich > T +43 732 2468 4286 <+43%20732%2024684286> > ilko.kovacic(a)jku.at > www.dke.jku.at >

1 0

Java Modules - Constructor
by kovacic 05 May '17

05 May '17

Hi all, I am running BaseX 8.6.3 currently and struggling with the inclusion of modules written in Java. I have extended the Hello World example: package org.basex.modules; public class Hello { private String str = "BaseX"; public Hello() {} public Hello(String str) { this.str = str; } public String hello(final String world) { return "Hello " + world; } public String hello() { return "Hello " + str; } } I can pack it into a jar-file and install it successfully. My jar-file is structured as following: hello.jar - META-INF - MANIFEST.MF - org - basex - modules - Hello.class Here is the content of my manifest.mf: Manifest-Version: 1.0 Main-Class: org.basex.modules.Hello The methods of the Hello-class can be called without any problems when the module is imported: import module namespace t='org.basex.modules.Hello'; t:hello('text') However, when I try to explicitly create the object by calling the constructor (new) with arguments it fails: declare namespace t='org.basex.modules.Hello'; let $obj := t:new('test') return '' When I try to call the constructor I receive the error [XPST0017] Unknown function: Q{org.basex.modules.Hello}new. Since I am able to execute the FileWriter example (http://docs.basex.org/wiki/Java_Bindings#Namespace_Declarations) which calls a constructor with an argument I would like to know if this behavior is a bug or if I am missing an important point. Regards, Ilko

2 1

BaseX scaling and real-time analytics
by Simon Wong 25 Apr '17

25 Apr '17

I'm doing a BaseX evaluation to characterize its performance with my use case. In my use case, I am receiving XML files over the network at a rate of about 100 / sec. I want to insert them into BaseX and perform real-time analytics. These XML files ranges from 20 to 50 nodes and in general has a similar strucuture. I will be periodically running XQuerys on this dataset. I am using the network API in Python to add documents in a tight loop to determine throughput. I notice that when the database is empty, adding 1000 documents takes about 1 second. When the database is loaded up with 30,000 documents, adding these 1000 documents takes about 5 seconds. I was able to get much better scaling with AUTOFLUSH off, and periodically executing a flush command. So far with a million documents in the database, adding documents seem to take close to constant time which is great. I haven't gotten to optimizing queries yet. Doing some simple aggregate queries like count(//), it looks like the query time scales linearly with the number of documents in the database. Are there any general strategies to optimizing real-time analytics use cases? Any options that can be tuned to increase document insertion and query speeds and scaling? Or perhaps indexing options that might work better for a dataset that is always changing and increasing? Thanks, - Simon

2 1

db:backups, db:ouptut order of operations.
by France Baril 21 Apr '17

21 Apr '17

Hi, What am I doing wrong? It was my impression that db:ouput was not executed until the database updates were completed. However, when I execute: let $db-name := 'Inve' return ( db:create-backup($db-name), db:output(db:backups($db-name)) ) The list of backups returned doesn't include the backup just added by db:create-backup(). I just tried with 8.6.3 to make sure it wasn't an older issue. Thanks! -- France Baril Architecte documentaire / Documentation architect france.baril(a)architextus.com

2 4

Re: [basex-talk] Get session config info
by Bram Vanroy 20 Apr '17

20 Apr '17

Hi Christian Do you mean a basex admin, a sys admin, or something else? Thanks Op 20 apr. 2017 13:41 schreef Christian Grün <christian.gruen(a)gmail.com>: Hi Bram, Users with admin permissions can request the database path via "db:system()//dbpath". Hope this helps, Christian On Wed, Apr 19, 2017 at 2:13 PM, Bram Vanroy <bram.vanroy1(a)student.kuleuven.be> wrote: > Hi List > > > > In a .basex file we can set the destination of our database. If we then > create a server, and create a database using a client, the BaseX-files will > be created in that directory. Is it possible to get the path to this > directory from within the client? In Perl I tried running the following > command after looking through the basex client, but I got an ‘undef’: > > > > my $session = Session->new($host, $port, $user, $pw); > > my $t = $session->info; > > $session->close; > > > > print $t; > > > > Any ideas how to get the configuration values for a basex server from a > (Perl) client? > > > > Thank you > > > > > > Bram > >

2 1

Get session config info
by Bram Vanroy 20 Apr '17

20 Apr '17

Hi List In a .basex file we can set the destination of our database. If we then create a server, and create a database using a client, the BaseX-files will be created in that directory. Is it possible to get the path to this directory from within the client? In Perl I tried running the following command after looking through the basex client, but I got an 'undef': my $session = Session->new($host, $port, $user, $pw); my $t = $session->info; $session->close; print $t; Any ideas how to get the configuration values for a basex server from a (Perl) client? Thank you Bram

2 1

Re: [basex-talk] xquery:eval error propagation
by Iwan Briquemont 18 Apr '17

18 Apr '17

Dear Christian, Perfect! I had not seen that option yet. Thank you, Iwan Le 18 avr. 2017 12:16, "Christian Grün" <christian.gruen(a)gmail.com> a écrit : Dear Iwan, Thanks for the feature proposal. As you may have seen, the xquery:parse function provides a 'pass' option, which can be used to pass on the original error info [1]. I have now added this option to xquery:eval [2], and to all other functions that support the same options. Feedback on the latest stable snapshot is welcome [3]. Cheers, Christian [1] http://docs.basex.org/wiki/XQuery_Module#xquery:parse [2] http://docs.basex.org/wiki/XQuery_Module#xquery:eval [3] http://files.basex.org/releases/latest/ On Tue, Apr 18, 2017 at 11:28 AM, Iwan Briquemont <tracnar(a)gmail.com> wrote: > Hello, > > I use xquery:eval to evaluate some user provided queries. > > It works well but when there is an error the true origin of the error > is hidden, as it will give the file and line of the xquery:eval call. > > Is there any way to pass the origin of the error through the > xquery:eval? > I guess the best would be to keep both origins. > > My workaround is to do a try/catch inside the evaluated query and wrap > the result with the error variables. It's a bit cumbersome and does not > work for static errors. > > Thank you, > Iwan

1 0

xquery:eval error propagation
by Iwan Briquemont 18 Apr '17

18 Apr '17

Hello, I use xquery:eval to evaluate some user provided queries. It works well but when there is an error the true origin of the error is hidden, as it will give the file and line of the xquery:eval call. Is there any way to pass the origin of the error through the xquery:eval? I guess the best would be to keep both origins. My workaround is to do a try/catch inside the evaluated query and wrap the result with the error variables. It's a bit cumbersome and does not work for static errors. Thank you, Iwan

2 1

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

BaseX-Talk