BaseX-Talk

basex-talk@mailman.uni-konstanz.de

4 participants
5268 discussions

BaseX 6.6.1
by Christian Grün 01 Apr '11

01 Apr '11

Dear all, thanks to everyone who gave us great feedback on BaseX 6.6, either by e-mail or directly at the XMLPrague conference! This way, we were able to finish Version 6.6.1 just one week later, which offers some exciting performance improvements and some more bug fixes: XQuery: [ADD] index rewritings added for .../text()[. = ..] syntax [ADD] optimizations of mixed axis path expressions, e.g.: //x/name() [MOD] index rewritings on collections fixed and generalized [MOD] faster evaluation of filters with pos. predicates, e.g.: $x[5] [FIX] fixed relocation of let clauses in GFLWOR expressions [FIX] trace function returned wrong original results [FIX] variables in catch clauses were discarded [FIX] HOF optimizations and fixes GUI: [FIX] language option (for Japanese, German, etc. interface) fixed To be continued, Christian BaseX Team, 2011

3 2

BaseX Issue Tracker
by Christian Grün 31 Mar '11

31 Mar '11

Hi, once again I'd like to remind all of you of our GitHub Issue Tracker, which lists some of the features to come next: https://github.com/BaseXdb/basex/issues You're invited to give your votes on the given issues, or add new entries. The more feedback we get, the better we'll be able to decide which features will be implemented first. Christian ___________________________ Christian Grün Uni KN, Box 188 78457 Konstanz, Germany http://www.inf.uni-konstanz.de/~gruen

1 0

abstract method error?
by Meredith Gregory 31 Mar '11

31 Mar '11

Dear BaseXes, i'm attempting to use the published API from Java (well Scala, really, but we're all JVM family, here...). i'm running into an abstract method error (see the trace below). Any clues would be gratefully appreciated. Best wishes, --greg scala> val db = Class.forName( "org.basex.api.xmldb.BXDatabase" ).newInstance().asInstanceOf[Database] val db = Class.forName( "org.basex.api.xmldb.BXDatabase" ).newInstance().asInstanceOf[Database] db: org.xmldb.api.base.Database = org.basex.api.xmldb.BXDatabase@69dbb4d1 scala> DatabaseManager.registerDatabase( db ) DatabaseManager.registerDatabase( db ) java.lang.AbstractMethodError: org.basex.api.xmldb.BXDatabase.getNames()[Ljava/lang/String; at org.xmldb.api.DatabaseManager.registerDatabase(Unknown Source) at .<init>(<console>:25) at .<clinit>(<console>) at RequestResult$.<init>(<console>:9) at RequestResult$.<clinit>(<console>) at RequestResult$scala_repl_result(<console>) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at scala.tools.nsc.Interpreter$Request$$anonfun$loadAndRun$1$$anonfun$apply$17.apply(Interpreter.scala:988) at scala.tools.nsc.Interpreter$Request$$anonfun$loadAndRun$1$$a... scala> -- L.G. Meredith Managing Partner Biosimilarity LLC 7329 39th Ave SW Seattle, WA 98136 +1 206.650.3740 http://biosimilarity.blogspot.com

3 8

Re: [basex-talk] Xquery through the PERL (or Java) API
by Isidro Vila Verde 30 Mar '11

30 Mar '11

Sorry!!! I am been in a process of focus in little details that I missed the most obvious: reboot the server. I just did that and (this) the problem disappear. I am going now to check if the update problem stills or also go disappear. Sorry the noise on the channel. Just a question. The GUI doesn't use the server to access to the DB? Isidro Em 30-03-2011 15:54, Isidro Vila Verde escreveu: > Dear Andreas, > > Thank you for you quick answer~. I didn't know about logs. It is in > fact a great help, but for presente it seems the query is correctly > received. > This is what I got > > 07:50:25.999 [127.0.0.1:39722] LOGIN serprest OK > 07:50:26.193 [127.0.0.1:39722] QUERY(0) declare > namespace saf="urn:OECD:StandardAuditFile-Tax:PT_1.00_01"; > declare option output:method "xml"; let $col := > collection('invoiceDB') let $invoice := > $col/saf:Invoice[saf:InvoiceNo/text() = '279'] return > $invoice OK > 07:50:26.193 [127.0.0.1:39722] QUERY(0) OK > 07:50:26.307 [127.0.0.1:39722] INIT(0) OK > 07:50:26.319 [127.0.0.1:39722] EXEC(0) OK > 07:50:26.320 [127.0.0.1:39722] INFO(0) OK > 07:50:26.320 [127.0.0.1:39722] CLOSE(0) OK > 07:50:26.347 [127.0.0.1:39722] LOGOUT serprest OK > > Regards > > Isidro > > Em 30-03-2011 15:45, Andreas Weiler escreveu: >> Dear Isidro, >> >> as a quick help, you could have a look at the log files on the >> server, they are located >> in your BaseXData folder (.logs). >> >> Here you can check if the query did arrive correctly at the server. >> >> -- Andreas >> >> Am 30.03.2011 um 16:39 schrieb Isidro Vila Verde: >> >>> Dear all, >>> >>> I have a very strange situation when invoking this xquery >>> >>> declare namespace saf="urn:OECD:StandardAuditFile-Tax:PT_1.00_01"; >>> declare option output:method "xml"; >>> >>> let $col := collection('invoiceDB') >>> let $invoice := $col/saf:Invoice[saf:InvoiceNo/text() = '279'] >>> return $invoice >>> >>> When invoked from GUI it returns the right XML element, but the same >>> query invoked through the perl (or java) API it returns a null result. >>> >>> Bellow is the perl (andf java version) code. What is more strange is >>> that it works for any other value of node saf:InvoiceNo/text(). It >>> just doesn't work for the value 279. >>> >>> In collection invoice DB each saf:Invoice is a single document and >>> the invoiceNo/text()='279' is the "last" document. The collection >>> was just created from a input directory and no other operations was >>> performed on it. >>> >>> Can you help please? >>> >>> I am using the last Basex 6.6 version on ubuntu with java-6-sun. >>> >>> I came to this error when I was in a process to identify why a >>> update operation through the perl API corrupted the database while >>> the same upadate query works fine when invoked from GUI. >>> So, my problem is not exactly this one but I can go any further >>> without resolving this. >>> >>> I notice, on page https://github.com/BaseXdb/BaseX, there is no API >>> version not the last basex 6.6. Should I go back to the version 6.5? >>> >>> >>> Thanks in advance for your help >>> >>> Isidro >>> >>> ------------------Perl Version----------------------------- >>> #!/usr/bin/perl >>> use strict; >>> use lib qw|/var/www/serprest/perl/3rd-party|; >>> use BaseXClient; >>> use warnings; >>> >>> eval { >>> my $session = Session->new("localhost", 1984, "serprest", >>> ".prest,ser"); >>> >>> my $q = q| >>> declare namespace >>> saf="urn:OECD:StandardAuditFile-Tax:PT_1.00_01"; >>> declare option output:method "xml"; >>> >>> let $col := collection('invoiceDB') >>> let $invoice := $col/saf:Invoice[saf:InvoiceNo/text() = >>> '279'] >>> return $invoice >>> |; >>> my $query = $session->query($q); >>> $query->init(); >>> print $query->execute(); >>> print $query->info(); >>> $query->close(); >>> $session->close(); >>> }; >>> >>> # print exception >>> print qq|<error>$@</error>| if $@; >>> >>> >>> ------------------Java Version----------------------------- >>> import java.io.IOException; >>> >>> public final class QueryTeste { >>> public static void main(final String[] args) { >>> try { >>> BaseXClient session = >>> new BaseXClient("localhost", 1984, "serprest", ".prest,ser"); >>> >>> try { >>> String input = "declare namespace >>> saf=\"urn:OECD:StandardAuditFile-Tax:PT_1.00_01\";" >>> + "declare option output:method \"xml\";" >>> + "let $col := collection('invoiceDB')" >>> + "let $invoice := $col/saf:Invoice[saf:InvoiceNo/text() >>> = '279']" >>> + "return $invoice"; >>> BaseXClient.Query query = session.query(input); >>> System.out.print(query.init()); >>> while(query.more()) { >>> System.out.println(query.next()); >>> } >>> System.out.print(query.close()); >>> } catch(IOException ex) { >>> ex.printStackTrace(); >>> } >>> session.close(); >>> } catch(IOException ex) { >>> ex.printStackTrace(); >>> } >>> } >>> } >>> ----------------------------------------------- >>> >>> >>> >>> >>> >>> >>> --- >>> avast! Antivirus: Outbound message clean. >>> Virus Database (VPS): 110330-0, 30-03-2011 >>> Tested on: 30-03-2011 15:39:30 >>> avast! - copyright (c) 1988-2011 AVAST Software. >>> http://www.avast.com >>> >>> >>> >>> _______________________________________________ >>> BaseX-Talk mailing list >>> BaseX-Talk(a)mailman.uni-konstanz.de >>> https://mailman.uni-konstanz.de/mailman/listinfo/basex-talk >> >> >> --- >> avast! Antivirus: Inbound message clean. >> Virus Database (VPS): 110330-0, 30-03-2011 >> Tested on: 30-03-2011 15:47:51 >> avast! - copyright (c) 1988-2011 AVAST Software. >> http://www.avast.com >> >> >> > > > > --- > avast! Antivirus: Outbound message clean. > Virus Database (VPS): 110330-0, 30-03-2011 > Tested on: 30-03-2011 15:54:40 > avast! - copyright (c) 1988-2011 AVAST Software. > http://www.avast.com > > > > > > --- > avast! Antivirus: Inbound message clean. > Virus Database (VPS): 110330-0, 30-03-2011 > Tested on: 30-03-2011 16:16:17 > avast! - copyright (c) 1988-2011 AVAST Software. > http://www.avast.com > > > --- avast! Antivirus: Outbound message clean. Virus Database (VPS): 110330-0, 30-03-2011 Tested on: 30-03-2011 16:22:03 avast! - copyright (c) 1988-2011 AVAST Software. http://www.avast.com

4 7

Fwd: Xquery through the PERL (or Java) API
by Andreas Weiler 30 Mar '11

30 Mar '11

Forwarding to mailing list. Anfang der weitergeleiteten E-Mail: > Von: Isidro Vila Verde <jvverde(a)gmail.com> > Datum: 30. März 2011 16:54:37 MESZ > An: Andreas Weiler <andreas.weiler(a)uni-konstanz.de> > Betreff: Re: [basex-talk] Xquery through the PERL (or Java) API > > Dear Andreas, > > Thank you for you quick answer~. I didn't know about logs. It is in fact a great help, but for presente it seems the query is correctly received. > This is what I got > > 07:50:25.999 [127.0.0.1:39722] LOGIN serprest OK > 07:50:26.193 [127.0.0.1:39722] QUERY(0) declare namespace saf="urn:OECD:StandardAuditFile-Tax:PT_1.00_01"; declare option output:method "xml"; let $col := collection('invoiceDB') let $invoice := $col/saf:Invoice[saf:InvoiceNo/text() = '279'] return $invoice OK > 07:50:26.193 [127.0.0.1:39722] QUERY(0) OK > 07:50:26.307 [127.0.0.1:39722] INIT(0) OK > 07:50:26.319 [127.0.0.1:39722] EXEC(0) OK > 07:50:26.320 [127.0.0.1:39722] INFO(0) OK > 07:50:26.320 [127.0.0.1:39722] CLOSE(0) OK > 07:50:26.347 [127.0.0.1:39722] LOGOUT serprest OK > > Regards > > Isidro > > Em 30-03-2011 15:45, Andreas Weiler escreveu: >> Dear Isidro, >> >> as a quick help, you could have a look at the log files on the server, they are located >> in your BaseXData folder (.logs). >> >> Here you can check if the query did arrive correctly at the server. >> >> -- Andreas >> >> Am 30.03.2011 um 16:39 schrieb Isidro Vila Verde: >> >>> Dear all, >>> >>> I have a very strange situation when invoking this xquery >>> >>> declare namespace saf="urn:OECD:StandardAuditFile-Tax:PT_1.00_01"; >>> declare option output:method "xml"; >>> >>> let $col := collection('invoiceDB') >>> let $invoice := $col/saf:Invoice[saf:InvoiceNo/text() = '279'] >>> return $invoice >>> >>> When invoked from GUI it returns the right XML element, but the same query invoked through the perl (or java) API it returns a null result. >>> >>> Bellow is the perl (andf java version) code. What is more strange is that it works for any other value of node saf:InvoiceNo/text(). It just doesn't work for the value 279. >>> >>> In collection invoice DB each saf:Invoice is a single document and the invoiceNo/text()='279' is the "last" document. The collection was just created from a input directory and no other operations was performed on it. >>> >>> Can you help please? >>> >>> I am using the last Basex 6.6 version on ubuntu with java-6-sun. >>> >>> I came to this error when I was in a process to identify why a update operation through the perl API corrupted the database while the same upadate query works fine when invoked from GUI. >>> So, my problem is not exactly this one but I can go any further without resolving this. >>> >>> I notice, on page https://github.com/BaseXdb/BaseX, there is no API version not the last basex 6.6. Should I go back to the version 6.5? >>> >>> >>> Thanks in advance for your help >>> >>> Isidro >>> >>> ------------------Perl Version----------------------------- >>> #!/usr/bin/perl >>> use strict; >>> use lib qw|/var/www/serprest/perl/3rd-party|; >>> use BaseXClient; >>> use warnings; >>> >>> eval { >>> my $session = Session->new("localhost", 1984, "serprest", ".prest,ser"); >>> >>> my $q = q| >>> declare namespace saf="urn:OECD:StandardAuditFile-Tax:PT_1.00_01"; >>> declare option output:method "xml"; >>> >>> let $col := collection('invoiceDB') >>> let $invoice := $col/saf:Invoice[saf:InvoiceNo/text() = '279'] >>> return $invoice >>> |; >>> my $query = $session->query($q); >>> $query->init(); >>> print $query->execute(); >>> print $query->info(); >>> $query->close(); >>> $session->close(); >>> }; >>> >>> # print exception >>> print qq|<error>$@</error>| if $@; >>> >>> >>> ------------------Java Version----------------------------- >>> import java.io.IOException; >>> >>> public final class QueryTeste { >>> public static void main(final String[] args) { >>> try { >>> BaseXClient session = >>> new BaseXClient("localhost", 1984, "serprest", ".prest,ser"); >>> >>> try { >>> String input = "declare namespace saf=\"urn:OECD:StandardAuditFile-Tax:PT_1.00_01\";" >>> + "declare option output:method \"xml\";" >>> + "let $col := collection('invoiceDB')" >>> + "let $invoice := $col/saf:Invoice[saf:InvoiceNo/text() = '279']" >>> + "return $invoice"; >>> BaseXClient.Query query = session.query(input); >>> System.out.print(query.init()); >>> while(query.more()) { >>> System.out.println(query.next()); >>> } >>> System.out.print(query.close()); >>> } catch(IOException ex) { >>> ex.printStackTrace(); >>> } >>> session.close(); >>> } catch(IOException ex) { >>> ex.printStackTrace(); >>> } >>> } >>> } >>> ----------------------------------------------- >>> >>> >>> >>> >>> >>> >>> --- >>> avast! Antivirus: Outbound message clean. >>> Virus Database (VPS): 110330-0, 30-03-2011 >>> Tested on: 30-03-2011 15:39:30 >>> avast! - copyright (c) 1988-2011 AVAST Software. >>> http://www.avast.com >>> >>> >>> >>> _______________________________________________ >>> BaseX-Talk mailing list >>> BaseX-Talk(a)mailman.uni-konstanz.de >>> https://mailman.uni-konstanz.de/mailman/listinfo/basex-talk >> >> >> --- >> avast! Antivirus: Inbound message clean. >> Virus Database (VPS): 110330-0, 30-03-2011 >> Tested on: 30-03-2011 15:47:51 >> avast! - copyright (c) 1988-2011 AVAST Software. >> http://www.avast.com >> >> >> > > > > --- > avast! Antivirus: Outbound message clean. > Virus Database (VPS): 110330-0, 30-03-2011 > Tested on: 30-03-2011 15:54:40 > avast! - copyright (c) 1988-2011 AVAST Software. > http://www.avast.com > > >

2 1

Xquery through the PERL (or Java) API
by Isidro Vila Verde 30 Mar '11

30 Mar '11

Dear all, I have a very strange situation when invoking this xquery declare namespace saf="urn:OECD:StandardAuditFile-Tax:PT_1.00_01"; declare option output:method "xml"; let $col := collection('invoiceDB') let $invoice := $col/saf:Invoice[saf:InvoiceNo/text() = '279'] return $invoice When invoked from GUI it returns the right XML element, but the same query invoked through the perl (or java) API it returns a null result. Bellow is the perl (andf java version) code. What is more strange is that it works for any other value of node saf:InvoiceNo/text(). It just doesn't work for the value 279. In collection invoice DB each saf:Invoice is a single document and the invoiceNo/text()='279' is the "last" document. The collection was just created from a input directory and no other operations was performed on it. Can you help please? I am using the last Basex 6.6 version on ubuntu with java-6-sun. I came to this error when I was in a process to identify why a update operation through the perl API corrupted the database while the same upadate query works fine when invoked from GUI. So, my problem is not exactly this one but I can go any further without resolving this. I notice, on page https://github.com/BaseXdb/BaseX, there is no API version not the last basex 6.6. Should I go back to the version 6.5? Thanks in advance for your help Isidro ------------------Perl Version----------------------------- #!/usr/bin/perl use strict; use lib qw|/var/www/serprest/perl/3rd-party|; use BaseXClient; use warnings; eval { my $session = Session->new("localhost", 1984, "serprest", ".prest,ser"); my $q = q| declare namespace saf="urn:OECD:StandardAuditFile-Tax:PT_1.00_01"; declare option output:method "xml"; let $col := collection('invoiceDB') let $invoice := $col/saf:Invoice[saf:InvoiceNo/text() = '279'] return $invoice |; my $query = $session->query($q); $query->init(); print $query->execute(); print $query->info(); $query->close(); $session->close(); }; # print exception print qq|<error>$@</error>| if $@; ------------------Java Version----------------------------- import java.io.IOException; public final class QueryTeste { public static void main(final String[] args) { try { BaseXClient session = new BaseXClient("localhost", 1984, "serprest", ".prest,ser"); try { String input = "declare namespace saf=\"urn:OECD:StandardAuditFile-Tax:PT_1.00_01\";" + "declare option output:method \"xml\";" + "let $col := collection('invoiceDB')" + "let $invoice := $col/saf:Invoice[saf:InvoiceNo/text() = '279']" + "return $invoice"; BaseXClient.Query query = session.query(input); System.out.print(query.init()); while(query.more()) { System.out.println(query.next()); } System.out.print(query.close()); } catch(IOException ex) { ex.printStackTrace(); } session.close(); } catch(IOException ex) { ex.printStackTrace(); } } } ----------------------------------------------- --- avast! Antivirus: Outbound message clean. Virus Database (VPS): 110330-0, 30-03-2011 Tested on: 30-03-2011 15:39:30 avast! - copyright (c) 1988-2011 AVAST Software. http://www.avast.com

2 1

Re: [basex-talk] Out of memory
by Christian Grün 30 Mar '11

30 Mar '11

Hi Rupert, nice to hear that! Btw, I've added a little optimizations for mixed location paths (as the one containing the name() function after the location steps), which should perform the discussed optimizations on-the-fly: http://files.basex.org/releases/latest/ It's recommended to switch to that latest snapshot anyway, as it fixes some important index rewritings on collections, which have been temporarily removed in Version 6.6. More feedback is welcome, Christian ____________________________ > Hello Christian! > > You're my personal hero! The query > "dinstinct-values(/descendant::*[randnr]/name())" worked perfectly! 2 GB of > data analysed in 3 seconds, WOW! > > > Greetings and thanks again! > Rupert Jung > > -- > Rupert Jung > <pagina> GmbH > Gesamtherstellung wissenschaftlicher Werke > Herrenberger Str. 51 > D-72070 Tübingen > Handelsregister Stuttgart HRB 380249 > Geschäftsführer: Tobias Ott > > E-Mail: rupert.jung(a)pagina-tuebingen.de > Phone: (0 70 71) 98 76-37 > Fax: (0 70 71) 98 76-22 > > http://www.pagina-online.de > > > -----Ursprüngliche Nachricht----- > Von: Christian Grün [mailto:christian.gruen@gmail.com] > Gesendet: Dienstag, 29. März 2011 18:51 > An: rupert.jung(a)pagina-tuebingen.de > Cc: Andreas Weiler; bjoern.duenckel(a)pagina-tuebingen.de; > basex-talk(a)mailman.uni-konstanz.de > Betreff: Re: [basex-talk] Out of memory > > Rupert, > > thanks for your observation. My assumption is that the (hidden) > descendant-or-self step in your query causes a huge number of > intermediary nodes, which are then reduced to a small result set. In > other words, your query.. > > dinstinct-values(//*[randnr]/name()) > > ..equals the following query: > > > dinstinct-values(/descendant-or-self::node()/child::*[child::randnr]/name()) > > There are several choices how to possibly speed up your query; please > try e.g. to: > > 1. explicitly use the descendant step: > dinstinct-values(/descendant::*[randnr]/name()) > 2. wrap the name function around the location path: > dinstinct-values( name( //*[randnr] )) > 3. directly address the randnr nodes and use a parent step: > dinstinct-values( name( /descendant::randnr/.. )) > > We might add some optimizations to BaseX to automatize some of the > proposed steps. > > If this doesn't help, feel free to give us more feedback. > > Best, > Christian > ___________________________ > > On Tue, Mar 29, 2011 at 5:31 PM, Rupert jung > <rupert.jung(a)pagina-tuebingen.de> wrote: >> Hi Andreas and thanks for your answer, >> >> >> >> unfortunely that didn’t work (java.exe consumed 1.2 GB, then stopped). The >> expected result should not be longer then about 10 element names or so... >> >> >> >> Maybe this could be a bug in basex itself…? >> >> >> >> >> >> ________________________________ >> >> Rupert Jung >> >> <pagina> GmbH >> Gesamtherstellung wissenschaftlicher Werke >> Herrenberger Str. 51 >> D-72070 Tübingen >> >> Handelsregister Stuttgart HRB 380249 >> Geschäftsführer: Tobias Ott >> >> Phone: (0 70 71) 98 76-37 >> Fax: (0 70 71) 98 76-22 >> E-Mail: rupert.jung(a)pagina-tuebingen.de >> http://www.pagina-online.de >> >> >> >> Von: Andreas Weiler [mailto:andreas.weiler@uni-konstanz.de] >> Gesendet: Dienstag, 29. März 2011 16:25 >> An: rupert.jung(a)pagina-tuebingen.de >> Cc: basex-talk(a)mailman.uni-konstanz.de; > bjoern.duenckel(a)pagina-tuebingen.de >> Betreff: Re: [basex-talk] Out of memory >> >> >> >> Hi, >> >> >> >> as first hint you could start BaseX with the Xmx flag of Java: >> >> >> >> java -cp BaseX.jar -Xmx1G org.basex.BaseXGUI >> >> >> >> Probably that will solve this issue. >> >> >> >> Kind regards, >> >> Andreas >> >> >> >> Am 29.03.2011 um 16:14 schrieb Rupert jung: >> >> Hi there, >> >> >> >> I’m currently doing some tests with BaseX and a mid-sized database (around > 2 >> GB). >> >> >> >> I wonder myself why I’m not able to process this xquery-statement: >> >> >> >> dinstinct-values(//*[randnr]/name()) >> >> („Give me a list of all elements which have a child-element <randnr> and >> remove all double entries“) >> >> >> >> After about 10 seconds a got a „out of main memory“ error. What’s really >> strange about this: Processing the nodes itself with //*[randnr]/ >> >> works like a charm (but gives me a HUGE amount of text and is not really >> useful for me at all). >> >> >> >> My system: win7-x64, 4 GB RAM, Java 1.6.0_21 >> >> >> >> Thank you in advance, >> >> Rupert Jung >> >> >> >> ________________________________ >> >> Rupert Jung >> >> <pagina> GmbH >> Gesamtherstellung wissenschaftlicher Werke >> Herrenberger Str. 51 >> D-72070 Tübingen >> >> Handelsregister Stuttgart HRB 380249 >> Geschäftsführer: Tobias Ott >> >> Phone: (0 70 71) 98 76-37 >> Fax: (0 70 71) 98 76-22 >> E-Mail: rupert.jung(a)pagina-tuebingen.de >> http://www.pagina-online.de >> >> >> >> _______________________________________________ >> BaseX-Talk mailing list >> BaseX-Talk(a)mailman.uni-konstanz.de >> https://mailman.uni-konstanz.de/mailman/listinfo/basex-talk >> >> >> >> _______________________________________________ >> BaseX-Talk mailing list >> BaseX-Talk(a)mailman.uni-konstanz.de >> https://mailman.uni-konstanz.de/mailman/listinfo/basex-talk >> >> > >

2 1

Re: [basex-talk] Out of memory
by Christian Grün 29 Mar '11

29 Mar '11

Rupert, thanks for your observation. My assumption is that the (hidden) descendant-or-self step in your query causes a huge number of intermediary nodes, which are then reduced to a small result set. In other words, your query.. dinstinct-values(//*[randnr]/name()) ..equals the following query: dinstinct-values(/descendant-or-self::node()/child::*[child::randnr]/name()) There are several choices how to possibly speed up your query; please try e.g. to: 1. explicitly use the descendant step: dinstinct-values(/descendant::*[randnr]/name()) 2. wrap the name function around the location path: dinstinct-values( name( //*[randnr] )) 3. directly address the randnr nodes and use a parent step: dinstinct-values( name( /descendant::randnr/.. )) We might add some optimizations to BaseX to automatize some of the proposed steps. If this doesn't help, feel free to give us more feedback. Best, Christian ___________________________ On Tue, Mar 29, 2011 at 5:31 PM, Rupert jung <rupert.jung(a)pagina-tuebingen.de> wrote: > Hi Andreas and thanks for your answer, > > > > unfortunely that didn’t work (java.exe consumed 1.2 GB, then stopped). The > expected result should not be longer then about 10 element names or so... > > > > Maybe this could be a bug in basex itself…? > > > > > > ________________________________ > > Rupert Jung > > <pagina> GmbH > Gesamtherstellung wissenschaftlicher Werke > Herrenberger Str. 51 > D-72070 Tübingen > > Handelsregister Stuttgart HRB 380249 > Geschäftsführer: Tobias Ott > > Phone: (0 70 71) 98 76-37 > Fax: (0 70 71) 98 76-22 > E-Mail: rupert.jung(a)pagina-tuebingen.de > http://www.pagina-online.de > > > > Von: Andreas Weiler [mailto:andreas.weiler@uni-konstanz.de] > Gesendet: Dienstag, 29. März 2011 16:25 > An: rupert.jung(a)pagina-tuebingen.de > Cc: basex-talk(a)mailman.uni-konstanz.de; bjoern.duenckel(a)pagina-tuebingen.de > Betreff: Re: [basex-talk] Out of memory > > > > Hi, > > > > as first hint you could start BaseX with the Xmx flag of Java: > > > > java -cp BaseX.jar -Xmx1G org.basex.BaseXGUI > > > > Probably that will solve this issue. > > > > Kind regards, > > Andreas > > > > Am 29.03.2011 um 16:14 schrieb Rupert jung: > > Hi there, > > > > I’m currently doing some tests with BaseX and a mid-sized database (around 2 > GB). > > > > I wonder myself why I’m not able to process this xquery-statement: > > > > dinstinct-values(//*[randnr]/name()) > > („Give me a list of all elements which have a child-element <randnr> and > remove all double entries“) > > > > After about 10 seconds a got a „out of main memory“ error. What’s really > strange about this: Processing the nodes itself with //*[randnr]/ > > works like a charm (but gives me a HUGE amount of text and is not really > useful for me at all). > > > > My system: win7-x64, 4 GB RAM, Java 1.6.0_21 > > > > Thank you in advance, > > Rupert Jung > > > > ________________________________ > > Rupert Jung > > <pagina> GmbH > Gesamtherstellung wissenschaftlicher Werke > Herrenberger Str. 51 > D-72070 Tübingen > > Handelsregister Stuttgart HRB 380249 > Geschäftsführer: Tobias Ott > > Phone: (0 70 71) 98 76-37 > Fax: (0 70 71) 98 76-22 > E-Mail: rupert.jung(a)pagina-tuebingen.de > http://www.pagina-online.de > > > > _______________________________________________ > BaseX-Talk mailing list > BaseX-Talk(a)mailman.uni-konstanz.de > https://mailman.uni-konstanz.de/mailman/listinfo/basex-talk > > > > _______________________________________________ > BaseX-Talk mailing list > BaseX-Talk(a)mailman.uni-konstanz.de > https://mailman.uni-konstanz.de/mailman/listinfo/basex-talk > >

2 1

Re: [basex-talk] Out of memory
by Dimitar Popov 29 Mar '11

29 Mar '11

Hi Rupert, could you post the execution plans of the two queries? And also the version of BaseX that you use. Best regards, Dimitar Am Dienstag 29 März 2011, 17:31:26 schrieb Rupert jung: > Hi Andreas and thanks for your answer, > > > > unfortunely that didnt work (java.exe consumed 1.2 GB, then stopped). The > expected result should not be longer then about 10 element names or so... > > > > Maybe this could be a bug in basex itself? > > > > > > _____ > > Rupert Jung > > <pagina> GmbH > Gesamtherstellung wissenschaftlicher Werke > Herrenberger Str. 51 > D-72070 Tübingen > > Handelsregister Stuttgart HRB 380249 > Geschäftsführer: Tobias Ott > > Phone: (0 70 71) 98 76-37 > Fax: (0 70 71) 98 76-22 > E-Mail: rupert.jung(a)pagina-tuebingen.de > http://www.pagina-online.de <http://www.pagina-online.de/> > > > > Von: Andreas Weiler [mailto:andreas.weiler@uni-konstanz.de] > Gesendet: Dienstag, 29. März 2011 16:25 > An: rupert.jung(a)pagina-tuebingen.de > Cc: basex-talk(a)mailman.uni-konstanz.de; bjoern.duenckel(a)pagina-tuebingen.de > Betreff: Re: [basex-talk] Out of memory > > > > Hi, > > > > as first hint you could start BaseX with the Xmx flag of Java: > > > > java -cp BaseX.jar -Xmx1G org.basex.BaseXGUI > > > > Probably that will solve this issue. > > > > Kind regards, > > Andreas > > > > Am 29.03.2011 um 16:14 schrieb Rupert jung: > > > > > > Hi there, > > > > Im currently doing some tests with BaseX and a mid-sized database (around > 2 GB). > > > > I wonder myself why Im not able to process this xquery-statement: > > > > dinstinct-values(//*[randnr]/name()) > > (Give me a list of all elements which have a child-element <randnr> and > remove all double entries) > > > > After about 10 seconds a got a out of main memory error. Whats really > strange about this: Processing the nodes itself with //*[randnr]/ > > works like a charm (but gives me a HUGE amount of text and is not really > useful for me at all). > > > > My system: win7-x64, 4 GB RAM, Java 1.6.0_21 > > > > Thank you in advance, > > Rupert Jung > > > > _____ > > Rupert Jung > > <pagina> GmbH > Gesamtherstellung wissenschaftlicher Werke > Herrenberger Str. 51 > D-72070 Tübingen > > Handelsregister Stuttgart HRB 380249 > Geschäftsführer: Tobias Ott > > Phone: (0 70 71) 98 76-37 > Fax: (0 70 71) 98 76-22 > E-Mail: rupert.jung(a)pagina-tuebingen.de > http://www.pagina-online.de <http://www.pagina-online.de/> > > > > _______________________________________________ > BaseX-Talk mailing list > BaseX-Talk(a)mailman.uni-konstanz.de > https://mailman.uni-konstanz.de/mailman/listinfo/basex-talk

2 1

Re: [basex-talk] Out of memory
by Andreas Weiler 29 Mar '11

29 Mar '11

Hi, as first hint you could start BaseX with the Xmx flag of Java: java -cp BaseX.jar -Xmx1G org.basex.BaseXGUI Probably that will solve this issue. Kind regards, Andreas Am 29.03.2011 um 16:14 schrieb Rupert jung: > Hi there, > > I’m currently doing some tests with BaseX and a mid-sized database (around 2 GB). > > I wonder myself why I’m not able to process this xquery-statement: > > dinstinct-values(//*[randnr]/name()) > („Give me a list of all elements which have a child-element <randnr> and remove all double entries“) > > After about 10 seconds a got a „out of main memory“ error. What’s really strange about this: Processing the nodes itself with //*[randnr]/ > works like a charm (but gives me a HUGE amount of text and is not really useful for me at all). > > My system: win7-x64, 4 GB RAM, Java 1.6.0_21 > > Thank you in advance, > Rupert Jung > > Rupert Jung > > <pagina> GmbH > Gesamtherstellung wissenschaftlicher Werke > Herrenberger Str. 51 > D-72070 Tübingen > Handelsregister Stuttgart HRB 380249 > Geschäftsführer: Tobias Ott > Phone: (0 70 71) 98 76-37 > Fax: (0 70 71) 98 76-22 > E-Mail: rupert.jung(a)pagina-tuebingen.de > http://www.pagina-online.de > > _______________________________________________ > BaseX-Talk mailing list > BaseX-Talk(a)mailman.uni-konstanz.de > https://mailman.uni-konstanz.de/mailman/listinfo/basex-talk

2 1

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

BaseX-Talk