BaseX-Talk

basex-talk@mailman.uni-konstanz.de

9 participants
5241 discussions

Possible to store query on the server side, but payload (XML data) in HTTP post, using jax-rx?
by Computer Software Developer 09 May '11

09 May '11

Hi, Using the run parameter in a jax-rx request, one can specify a query contained in a file stored on the server side. Using HTTP Post, one can specify the xquery and the payload in the HTTP request as XML. If the XML is generated on the client side to be stored on the server using HTTP post, can one execute an updating xquery stored on the server side to store this generated XML on the server? In other words, (how) can one run xqueries stored on the server side with an XML payload submitted using the HTTP post? Thanks.

2 10

Insert nodes in large xml structures generates Exception
by augras philippe 09 May '11

09 May '11

Hello , i send you the following bug trace ....and ask you why the xq correctly works with small xml structure and not with largest ! Details here : Small structure is 12Mg, 130Knodes and 5 Heigh ( 2K incoming Objects ) Largest structure is 43Mg, 2000K nodes and 5 Heigh ( 75K incoming Objects ) DB creation trace is : SET PARSER xml PARSER: xml Command: SET PARSEROPT lines=true,format=verbose,header=true,separator=comma PARSEROPT: lines=true,format=verbose,header=true,separator=comma Command: CREATE DB ea_i_co_o_o E:/ENV_Inst/TrioX/ScriptAUP/EA/i/TKE/co.o.o/co_o_o.xml Database 'ea_i_co_o_o' created in 8158.29 ms. Bugs trace is : "Possible bug? Your feedback is welcome: Contact: basex-talk(a)mailman.uni-konstanz.de Version: BaseX 6.5.1 Java: Sun Microsystems Inc., 1.6.0_25 OS: Windows XP, x86 Stack Trace: java.lang.ArrayIndexOutOfBoundsException: 25864888 org.basex.io.TableDiskAccess.write4(TableDiskAccess.java:156) org.basex.data.Data.size(Data.java:747) org.basex.data.Data.insert(Data.java:716)" Now i explain how it occurs . My project is to migrate xml structure in new xml structure, i use xq to change progressivly the xml schema It is important for me to check that is can handle xml structure with 200 K objects definition , with about 10-100 attributs definition each. then i've setup a set of small 4 xq file in charge to generate progressivly "the compliant xml structure " for everying incoming Object. Simply , On every incoming object ( Object node ) i add a small Product node with his definition in a first xq , I proceed the same with ( Form node ) and ( ProductRevision node ) and their own xml content ( all about 10 node each ) This was working fine in a small structure , update is done in 10 second and it is fine, so how can i do this with larger structure. In addition , i've limited the nb of object in selection of the update ( position < 250 ) and the result is not good , , Should i deduce that inserting nodes is not recommended in my case study ? PS : i've setup the nodes and attributes index, not the full text ( i never use text node ) and i run baseX651. Bests Regards XQ details here : for $ea_i in $i_type_in let $ApplicationRef := local:build_ApplicationRef($ea_i,"<A/>") let $AssociatedForm := local:build_AssociatedForm ($ea_i,"<A/>") let $UserData := local:build_UserData ($ea_i,"<A/>") let $m := ( $ApplicationRef , $UserData, $AssociatedForm ) let $ProductRevision := local:build_ProductRevision($ea_i,$m) let $out := ($ProductRevision) return (delete node$ea_i/ProductRevision, insert node $out into $ea_i[1]) (:return $out :)

2 1

Re: [basex-talk] What happened to the DeepFS menu? Was it removed?
by John D. Mitchell 08 May '11

08 May '11

Howdy, Just upgraded to the latest Base-x v6.6.1 and the create command no longer accepts "fs" as one of the types. I've been using DeepFS and so this is a bit of an issue. :-) Note also that "mab" is listed in the auto-complete list but is also excluded. Thanks, John

5 4

Possible bug in GUI corrupts database
by Thomas Kaltofen 08 May '11

08 May '11

Hi, I think I found a bug in the GUI which corrupts the database. Steps to reproduce: - Create database 'db1' - Add some documents to database 'db1' through server interface (not through GUI) - Now start GUI and open 'db1' - Add some more documents to database 'db1' through server interface (keep GUI open) - If one re-opens 'db1' now in GUI, database gets corrupted and GUI goes crazy Best regards, Thomas

2 3

XML encoding problem
by Mike Cobo 06 May '11

06 May '11

Hi, I have a collection of XML documents in which I want to replace only one attribute per file. The XML documents contain some XML entities for German "Umlaute" characters (eg. ü). After running the XQuery script which replaces the attributes, I use the "Export XML" function of the GUI to export the modified documents to a local folder. Unfortunaltey, the XML entities are now replaced by the corresponding "real" character (eg. ü). I tried the several parsing options of the "Create database" dialog, but already when creating the DB I can see the "real" character in the GUI text output window. As I don't wanna change anything else of the original XML content butthe attribute, I need the output files to have the XML entities instead of the "real" characters (as in the original files). Here an simple example original file: <?xml version="1.0" encoding="UTF-8"?> <Message xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> <header messageId="4523251"> </header> <dataSupply> <supplyProperty description="Gültigkeitsbeginn" value="12.12.2010"/> </dataSupply> </Message> And here's what I get as output: <?xml version="1.0" encoding="UTF-8"?> <Message xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> <header messageId="000"/> <dataSupply> <supplyProperty description="Gültigkeitsbeginn" value="12.12.2010"/> </dataSupply> </Message> How can I get the export encoding right? best regards, Mike

2 1

Help on BaseX commands
by Christian Grün 06 May '11

06 May '11

Dear all, we have improved our documentation on the BaseX database commands: http://docs.basex.org/wiki/Commands The next version of BaseX will be released in just a few days. Enjoy, Christian ___________________________ Christian Grün BaseX Team Uni KN, Box 188 78457 Konstanz, Germany http://www.inf.uni-konstanz.de/~gruen

1 0

Concurrency with the server API under high load
by Jason Klassen 05 May '11

05 May '11

Hi, I'm seeking some help on the best way to use BaseX in a highly concurrent environment. We're using the server API to interact with a BaseX 6.6 server and noticing some very odd behavior when 100+ threads use clientsession concurrently to access the same db. Looking at the BaseX logs I get some correct lines like: 01:19:21.101 [127.0.0.1:33153] OPEN Async_StressTestDB_Med 01:19:22.301 [127.0.0.1:33274] XQUERY insert node <record><contentChannel><String>data2</String></contentChannel><String>v alue goes here618</String></record> into for $db in collection('Async_StressTestDB_Med')/records return $db But then I also get lines like: 01:19:21.105 [127.0.0.1:33161] OPEONP EANs yAnscy_nSct_rSetsrseTsessTteDsBt_DMBe_dM Error: Stopped at line 1, column 6: Unknown command 'OPEONP'; try "help". 01:19:21.112 [127.0.0.1:33156] OOPPEENN AAssyynncc__SSttrreessssTTeessttDDBB__MMeedd Error: Stopped at line 1, column 8: Unknown command 'OOPPEENN'; try "help". 01:19:23.065 [127.0.0.1:33642] XQXERY insYrt ninserde <tr ecord><code nrecord><ctnteneChanntChannel><etl><Strirg>data2i/Strg>datng><a/2content C/Striang>nnel><Stcintenng>value Channeloes hereString>va<uStrine>< goecord>esn hert152o foring></rec rd>$db in collectiono'Async_ tressTestDor ddb in 'ollec/recoion('As nc_SteressTestDu_Med')/n $dbecords return $db Error: Stopped at line 1, column 6: Unknown command 'xqxery'; did you mean 'xquery'? The issue seems to happen when calling clientSession.execute(...) because I can verify that the command string being passed to execute is correct even when the log executes a mangled command. I believe 2 problems are happening to us. 1. A collection in clientSession is not thread safe when storing the commands passed to it. 2. BaseX is write locking the db on concurrent inserts. I understand the need for that but the wiki on Transaction Management implied that there was a queue where requests would wait if isolation could not be guaranteed. This sounded automatic. Are there any steps I need to take to enable the Transaction Management Queue? Below is the JUnit 4 test setup we're using to find the errors, generally I run 1 test at a time to observe and limit side effects. The BaseX GUI is closed while the tests run. I've also attached the full BaseX logs generated by running the tests but if they get removed I can easily email them upon request. How can the problem can be resolved? Thanks, Jason import org.junit._ import Assert._ import scala.util.Random import scala.concurrent.ops._ import scala.actors.Actor._ import org.basex.core.BaseXException import org.basex.core.cmd._ import org.basex.server.ClientSession import scala.xml._ class MockBaseXXMLStore { val dbHost = "localhost" val dbPort = "1984" val dbUser = "admin" val dbPwd = "admin" var _clientSession: Option[ClientSession] = None def clientSession: ClientSession = { _clientSession match { case Some(cs) => cs case None => { val cs = new ClientSession(dbHost, dbPort.toInt, dbUser, dbPwd) _clientSession = Some(cs) cs } } } def insertUpdate(xmlCollStr: String)(xmlElemStr: String): Unit = { val srvrRspStrm = new java.io.ByteArrayOutputStream() try { clientSession.setOutputStream(srvrRspStrm) clientSession.execute(new Open(xmlCollStr)) val insertTemplate = ( "insert node %NODE% into " + "for $db in collection('%COLLNAME%')/records return $db" ); val insertQry = insertTemplate.replace( "%NODE%", xmlElemStr ).replace( "%COLLNAME%", xmlCollStr ) try { clientSession.execute(new XQuery(insertQry)) } catch { case e: BaseXException => { } } } catch { case e: BaseXException => { val recordsElem = <records> {XML.loadString(xmlElemStr)} </records> clientSession.execute(new CreateDB(xmlCollStr)) clientSession.execute(new Add(recordsElem.toString)) } } finally { srvrRspStrm.close() } } } class BaseXTest { val rand = new Random() @Test //Success: 1 created def insertUpdate = { val db = new MockBaseXXMLStore db.insertUpdate("MockBaseXXMLStoreTestDB")("<record><contentChannel><Str ing>data2</String></contentChannel><String>value goes here" + rand.nextInt + "</String></record>") } @Test //Success: 100 and 1000 created def stressInsertUpdate = { val db = new MockBaseXXMLStore println("starting small") for (i <- 1 to 100) { db.insertUpdate("StressTestDB_Small")("<record><contentChannel><String>d ata2</String></contentChannel><String>value goes here" + i + "</String></record>") } println("starting med") for (i <- 1 to 1000) { db.insertUpdate("StressTestDB_Med")("<record><contentChannel><String>dat a2</String></contentChannel><String>value goes here" + i + "</String></record>") } } @Test //Fail: 0 and 184 created def stressInsertUpdateAsync = { val db = new MockBaseXXMLStore println("async starting small") for (i <- 1 to 100) { spawn { db.insertUpdate("Async_StressTestDB_Small")("<record><contentChannel><St ring>data2</String></contentChannel><String>value goes here" + i + "</String></record>") } } println("async starting med") for (i <- 1 to 1000) { spawn { db.insertUpdate("Async_StressTestDB_Med")("<record><contentChannel><Stri ng>data2</String></contentChannel><String>value goes here" + i + "</String></record>") } } } @Test //fail 4 and 0 created def stressInsertUpdateActor = { val db = new MockBaseXXMLStore println("async starting small") for (i <- 1 to 100) { actor { db.insertUpdate("Actor_StressTestDB_Small")("<record><contentChannel><St ring>data2</String></contentChannel><String>value goes here" + i + "</String></record>") } } println("async starting med") for (i <- 1 to 1000) { actor { db.insertUpdate("Actor_StressTestDB_Med")("<record><contentChannel><Stri ng>data2</String></contentChannel><String>value goes here" + i + "</String></record>") } } } }

3 8

collections in 6.5.1
by C. M. Sperberg-McQueen 04 May '11

04 May '11

Thanks to Christian Grün's prompt response to my question about attributes, I upgraded to Basex 6.5.1 the other day. And I've run into an unexpected behavior. I have several versions of the Unicode database in XML (the Unicode consortium started shipping XML versions with 5.1.0, and I've created XML documents with the information I need for all the earlier versions); they are all in directory ~/2011/Unicode. But when I ask to create a new database in the GUI, giving that directory as the path and accepting the default pattern of *.xml, the only document in the resulting database appears to be the small schemas.xml file that nXML mode placed in one of the subdirectories of ~/2011/Unicode when I edited an XSLT stylesheet there. What I was expecting was that all the XML documents in that subtree of the file directory would be added -- I think that was the behavior in earlier versions. Has something changed? Or have I gotten out of practice and done something wrong? I hope this is clear; I can try to explain further if needed. Thanks! -- **************************************************************** * C. M. Sperberg-McQueen, Black Mesa Technologies LLC * http://www.blackmesatech.com * http://cmsmcq.com/mib * http://balisage.net ****************************************************************

3 6

delete nodes ..
by Erol Akarsu 04 May '11

04 May '11

I tried to delete some nodes with "delete nodes .." xquery update command. It actually did what was requested. I checked the database size that is still same as previous one. I know the nodes deleted has a lot of data and I think database indexes would be adjusted accordingly. Then, I exported database as xml file and recreated db. I can see it has real size. My question is why DB is not adjusting indexes when nodes deleted? Thanks Erol Akarsu On Fri, Apr 29, 2011 at 9:23 AM, Erol Akarsu <eakarsu(a)gmail.com> wrote: > Hi, > > Have we thought on clustering basex servers so we can partition xml > documents? > > Here, I am only interested in a global partitioning: > > Let's say if we have xml document like this, I would like to partition > RECORDS content so that each host will have equal number of RECORD elements. > Then, we need to aggregate results of individual hosts. > Can we implement this simple clustering framework with Basex? > > > <RECORDS> > <RECORD> > ..... > </RECORD> > <RECORD> > ..... > </RECORD> > </RECORDS> > > On Mon, Apr 11, 2011 at 12:35 PM, Erol Akarsu <eakarsu(a)gmail.com> wrote: > >> Ok, >> >> I was able to run full text search with another XML Database. >> >> I am primarily interested in how Basex will play with big XML file >> Wikipedia. >> >> Actually, Database create of wikipedia is fine. But when I add full tet >> search and indexes for it, it always throws out of memory exception error. >> >> I have changed -Xmx with 6GB that is still not enough to generate indexes >> for Wikipedia. >> >> Can you help me on how to generate indexes with a machine that case 6GB >> for Basex process? >> >> Thanks >> >> Erol Akarsu >> >> >> >> On Sun, Apr 10, 2011 at 4:07 AM, Andreas Weiler < >> andreas.weiler(a)uni-konstanz.de> wrote: >> >>> Hi, >>> >>> the following query could work for you: >>> >>> declare namespace w="http://www.mediawiki.org/xml/export-0.5/"; >>> for $i in doc("enwiki-latest-pages-articles")//w:sitename >>> return $i[. contains text "Wikipedia"]/.. >>> >>> -- Andreas >>> >>> Am 09.04.2011 um 20:43 schrieb Erol Akarsu: >>> >>> Hi >>> >>> I am having difficulty in running full text operators. This script gives >>> siteinfo below >>> declare namespace w="http://www.mediawiki.org/xml/export-0.5/"; >>> let $d := fn:doc ("enwiki-latest-pages-articles") >>> return ($d//w:siteinfo)[1] >>> >>> But return $d//w:siteinfo[w:sitename contains text 'Wikipedia'] does NOT >>> give same node >>> Why "contains" ft operator behave incorrectly? I remember it was working >>> fine. I just dropped and recreated database and turn all indexes. Can you >>> help me? >>> Query info is here: >>> >>> Query: declare namespace w="http://www.mediawiki.org/xml/export-0.5/"; >>> Compiling: >>> - pre-evaluating fn:doc("enwiki-latest-pages-articles") >>> - adding text() step >>> - optimizing descendant-or-self step(s) >>> - removing path with no index results >>> - pre-evaluating (())[1] >>> - binding static variable $res >>> - pre-evaluating fn:doc("enwiki-latest-pages-articles") >>> - binding static variable $d >>> - adding text() step >>> - optimizing descendant-or-self step(s) >>> - removing path with no index results >>> - simplifying flwor expression >>> Result: () >>> Timing: >>> - Parsing: 0.46 ms >>> - Compiling: 0.42 ms >>> - Evaluating: 0.17 ms >>> - Printing: 0.1 ms >>> - Total Time: 1.15 ms >>> Query plan: >>> <sequence size="0"/> >>> >>> >>> >>> <siteinfo xmlns="http://www.mediawiki.org/xml/export-0.5/" xmlns:xsi=" >>> http://www.w3.org/2001/XMLSchema-instance"> >>> <sitename>Wikipedia</sitename> >>> <base>http://en.wikipedia.org/wiki/Main_Page</base> >>> <generator>MediaWiki 1.17wmf1</generator> >>> <case>first-letter</case> >>> <namespaces> >>> <namespace key="-2" case="first-letter">Media</namespace> >>> <namespace key="-1" case="first-letter">Special</namespace> >>> <namespace key="0" case="first-letter"/> >>> <namespace key="1" case="first-letter">Talk</namespace> >>> <namespace key="2" case="first-letter">User</namespace> >>> <namespace key="3" case="first-letter">User talk</namespace> >>> <namespace key="4" case="first-letter">Wikipedia</namespace> >>> <namespace key="5" case="first-letter">Wikipedia talk</namespace> >>> <namespace key="6" case="first-letter">File</namespace> >>> <namespace key="7" case="first-letter">File talk</namespace> >>> <namespace key="8" case="first-letter">MediaWiki</namespace> >>> <namespace key="9" case="first-letter">MediaWiki talk</namespace> >>> <namespace key="10" case="first-letter">Template</namespace> >>> <namespace key="11" case="first-letter">Template talk</namespace> >>> <namespace key="12" case="first-letter">Help</namespace> >>> <namespace key="13" case="first-letter">Help talk</namespace> >>> <namespace key="14" case="first-letter">Category</namespace> >>> <namespace key="15" case="first-letter">Category talk</namespace> >>> <namespace key="100" case="first-letter">Portal</namespace> >>> <namespace key="101" case="first-letter">Portal talk</namespace> >>> <namespace key="108" case="first-letter">Book</namespace> >>> <namespace key="109" case="first-letter">Book talk</namespace> >>> </namespaces> >>> </siteinfo> >>> >>> On Mon, Apr 4, 2011 at 7:31 AM, Erol Akarsu <eakarsu(a)gmail.com> wrote: >>> >>>> I imported wikipedia xml into basex and tried to search it. >>>> >>>> But searching it takes longer. >>>> >>>> I tried to search one element that is first child of whole document and >>>> it took 52 sec. >>>> I know the XML file is very big 31GB. How can I optimize the search? >>>> >>>> declare namespace w="http://www.mediawiki.org/xml/export-0.5/"; >>>> >>>> let $d := fn:doc ("enwiki-latest-pages-articles")//w:siteinfo >>>> return $d >>>> >>>> Database info: >>>> >>>> > open enwiki-latest-pages-articles >>>> Database 'enwiki-latest-pages-articles' opened in 778.49 ms. >>>> > info database >>>> Database Properties >>>> Name: enwiki-latest-pages-articles >>>> Size: 23356 MB >>>> Nodes: 228090153 >>>> Height: 6 >>>> >>>> Database Creation >>>> Path: /mnt/hgfs/C/tmp/enwiki-latest-pages-articles.xml >>>> Time Stamp: 03.04.2011 12:29:15 >>>> Input Size: 30025 MB >>>> Encoding: UTF-8 >>>> Documents: 1 >>>> Whitespace Chopping: ON >>>> Entity Parsing: OFF >>>> >>>> Indexes >>>> Up-to-date: true >>>> Path Summary: ON >>>> Text Index: ON >>>> Attribute Index: ON >>>> Full-Text Index: OFF >>>> > >>>> >>>> >>>> Timing info: >>>> >>>> Query: declare namespace w="http://www.mediawiki.org/xml/export-0.5/"; >>>> Compiling: >>>> - pre-evaluating fn:doc("enwiki-latest-pages-articles") >>>> - optimizing descendant-or-self step(s) >>>> - binding static variable $d >>>> - removing variable $d >>>> - simplifying flwor expression >>>> Result: element siteinfo { ... } >>>> Timing: >>>> - Parsing: 1.4 ms >>>> - Compiling: 52599.0 ms >>>> - Evaluating: 0.28 ms >>>> - Printing: 0.62 ms >>>> - Total Time: 52601.32 ms >>>> Query plan: >>>> <DBNode name="enwiki-latest-pages-articles" pre="5"/> >>>> >>>> >>>> >>>> Result of query: >>>> >>>> <siteinfo xmlns="http://www.mediawiki.org/xml/export-0.5/" xmlns:xsi=" >>>> http://www.w3.org/2001/XMLSchema-instance"> >>>> <sitename>Wikipedia</sitename> >>>> <base>http://en.wikipedia.org/wiki/Main_Page</base> >>>> <generator>MediaWiki 1.17wmf1</generator> >>>> <case>first-letter</case> >>>> <namespaces> >>>> <namespace key="-2" case="first-letter">Media</namespace> >>>> <namespace key="-1" case="first-letter">Special</namespace> >>>> <namespace key="0" case="first-letter"/> >>>> <namespace key="1" case="first-letter">Talk</namespace> >>>> <namespace key="2" case="first-letter">User</namespace> >>>> <namespace key="3" case="first-letter">User talk</namespace> >>>> <namespace key="4" case="first-letter">Wikipedia</namespace> >>>> <namespace key="5" case="first-letter">Wikipedia talk</namespace> >>>> <namespace key="6" case="first-letter">File</namespace> >>>> <namespace key="7" case="first-letter">File talk</namespace> >>>> <namespace key="8" case="first-letter">MediaWiki</namespace> >>>> <namespace key="9" case="first-letter">MediaWiki talk</namespace> >>>> <namespace key="10" case="first-letter">Template</namespace> >>>> <namespace key="11" case="first-letter">Template talk</namespace> >>>> <namespace key="12" case="first-letter">Help</namespace> >>>> <namespace key="13" case="first-letter">Help talk</namespace> >>>> <namespace key="14" case="first-letter">Category</namespace> >>>> <namespace key="15" case="first-letter">Category talk</namespace> >>>> <namespace key="100" case="first-letter">Portal</namespace> >>>> <namespace key="101" case="first-letter">Portal talk</namespace> >>>> <namespace key="108" case="first-letter">Book</namespace> >>>> <namespace key="109" case="first-letter">Book talk</namespace> >>>> </namespaces> >>>> </siteinfo> >>>> >>>> >>>> >>>> Thanks >>>> >>>> Erol Akarsu >>>> >>>> >>> _______________________________________________ >>> BaseX-Talk mailing list >>> BaseX-Talk(a)mailman.uni-konstanz.de >>> https://mailman.uni-konstanz.de/mailman/listinfo/basex-talk >>> >>> >>> >> >

2 3

Clustering of BaseX servers
by Erol Akarsu 29 Apr '11

29 Apr '11

Hi, Have we thought on clustering basex servers so we can partition xml documents? Here, I am only interested in a global partitioning: Let's say if we have xml document like this, I would like to partition RECORDS content so that each host will have equal number of RECORD elements. Then, we need to aggregate results of individual hosts. Can we implement this simple clustering framework with Basex? <RECORDS> <RECORD> ..... </RECORD> <RECORD> ..... </RECORD> </RECORDS> On Mon, Apr 11, 2011 at 12:35 PM, Erol Akarsu <eakarsu(a)gmail.com> wrote: > Ok, > > I was able to run full text search with another XML Database. > > I am primarily interested in how Basex will play with big XML file > Wikipedia. > > Actually, Database create of wikipedia is fine. But when I add full tet > search and indexes for it, it always throws out of memory exception error. > > I have changed -Xmx with 6GB that is still not enough to generate indexes > for Wikipedia. > > Can you help me on how to generate indexes with a machine that case 6GB > for Basex process? > > Thanks > > Erol Akarsu > > > > On Sun, Apr 10, 2011 at 4:07 AM, Andreas Weiler < > andreas.weiler(a)uni-konstanz.de> wrote: > >> Hi, >> >> the following query could work for you: >> >> declare namespace w="http://www.mediawiki.org/xml/export-0.5/"; >> for $i in doc("enwiki-latest-pages-articles")//w:sitename >> return $i[. contains text "Wikipedia"]/.. >> >> -- Andreas >> >> Am 09.04.2011 um 20:43 schrieb Erol Akarsu: >> >> Hi >> >> I am having difficulty in running full text operators. This script gives >> siteinfo below >> declare namespace w="http://www.mediawiki.org/xml/export-0.5/"; >> let $d := fn:doc ("enwiki-latest-pages-articles") >> return ($d//w:siteinfo)[1] >> >> But return $d//w:siteinfo[w:sitename contains text 'Wikipedia'] does NOT >> give same node >> Why "contains" ft operator behave incorrectly? I remember it was working >> fine. I just dropped and recreated database and turn all indexes. Can you >> help me? >> Query info is here: >> >> Query: declare namespace w="http://www.mediawiki.org/xml/export-0.5/"; >> Compiling: >> - pre-evaluating fn:doc("enwiki-latest-pages-articles") >> - adding text() step >> - optimizing descendant-or-self step(s) >> - removing path with no index results >> - pre-evaluating (())[1] >> - binding static variable $res >> - pre-evaluating fn:doc("enwiki-latest-pages-articles") >> - binding static variable $d >> - adding text() step >> - optimizing descendant-or-self step(s) >> - removing path with no index results >> - simplifying flwor expression >> Result: () >> Timing: >> - Parsing: 0.46 ms >> - Compiling: 0.42 ms >> - Evaluating: 0.17 ms >> - Printing: 0.1 ms >> - Total Time: 1.15 ms >> Query plan: >> <sequence size="0"/> >> >> >> >> <siteinfo xmlns="http://www.mediawiki.org/xml/export-0.5/" xmlns:xsi=" >> http://www.w3.org/2001/XMLSchema-instance"> >> <sitename>Wikipedia</sitename> >> <base>http://en.wikipedia.org/wiki/Main_Page</base> >> <generator>MediaWiki 1.17wmf1</generator> >> <case>first-letter</case> >> <namespaces> >> <namespace key="-2" case="first-letter">Media</namespace> >> <namespace key="-1" case="first-letter">Special</namespace> >> <namespace key="0" case="first-letter"/> >> <namespace key="1" case="first-letter">Talk</namespace> >> <namespace key="2" case="first-letter">User</namespace> >> <namespace key="3" case="first-letter">User talk</namespace> >> <namespace key="4" case="first-letter">Wikipedia</namespace> >> <namespace key="5" case="first-letter">Wikipedia talk</namespace> >> <namespace key="6" case="first-letter">File</namespace> >> <namespace key="7" case="first-letter">File talk</namespace> >> <namespace key="8" case="first-letter">MediaWiki</namespace> >> <namespace key="9" case="first-letter">MediaWiki talk</namespace> >> <namespace key="10" case="first-letter">Template</namespace> >> <namespace key="11" case="first-letter">Template talk</namespace> >> <namespace key="12" case="first-letter">Help</namespace> >> <namespace key="13" case="first-letter">Help talk</namespace> >> <namespace key="14" case="first-letter">Category</namespace> >> <namespace key="15" case="first-letter">Category talk</namespace> >> <namespace key="100" case="first-letter">Portal</namespace> >> <namespace key="101" case="first-letter">Portal talk</namespace> >> <namespace key="108" case="first-letter">Book</namespace> >> <namespace key="109" case="first-letter">Book talk</namespace> >> </namespaces> >> </siteinfo> >> >> On Mon, Apr 4, 2011 at 7:31 AM, Erol Akarsu <eakarsu(a)gmail.com> wrote: >> >>> I imported wikipedia xml into basex and tried to search it. >>> >>> But searching it takes longer. >>> >>> I tried to search one element that is first child of whole document and >>> it took 52 sec. >>> I know the XML file is very big 31GB. How can I optimize the search? >>> >>> declare namespace w="http://www.mediawiki.org/xml/export-0.5/"; >>> >>> let $d := fn:doc ("enwiki-latest-pages-articles")//w:siteinfo >>> return $d >>> >>> Database info: >>> >>> > open enwiki-latest-pages-articles >>> Database 'enwiki-latest-pages-articles' opened in 778.49 ms. >>> > info database >>> Database Properties >>> Name: enwiki-latest-pages-articles >>> Size: 23356 MB >>> Nodes: 228090153 >>> Height: 6 >>> >>> Database Creation >>> Path: /mnt/hgfs/C/tmp/enwiki-latest-pages-articles.xml >>> Time Stamp: 03.04.2011 12:29:15 >>> Input Size: 30025 MB >>> Encoding: UTF-8 >>> Documents: 1 >>> Whitespace Chopping: ON >>> Entity Parsing: OFF >>> >>> Indexes >>> Up-to-date: true >>> Path Summary: ON >>> Text Index: ON >>> Attribute Index: ON >>> Full-Text Index: OFF >>> > >>> >>> >>> Timing info: >>> >>> Query: declare namespace w="http://www.mediawiki.org/xml/export-0.5/"; >>> Compiling: >>> - pre-evaluating fn:doc("enwiki-latest-pages-articles") >>> - optimizing descendant-or-self step(s) >>> - binding static variable $d >>> - removing variable $d >>> - simplifying flwor expression >>> Result: element siteinfo { ... } >>> Timing: >>> - Parsing: 1.4 ms >>> - Compiling: 52599.0 ms >>> - Evaluating: 0.28 ms >>> - Printing: 0.62 ms >>> - Total Time: 52601.32 ms >>> Query plan: >>> <DBNode name="enwiki-latest-pages-articles" pre="5"/> >>> >>> >>> >>> Result of query: >>> >>> <siteinfo xmlns="http://www.mediawiki.org/xml/export-0.5/" xmlns:xsi=" >>> http://www.w3.org/2001/XMLSchema-instance"> >>> <sitename>Wikipedia</sitename> >>> <base>http://en.wikipedia.org/wiki/Main_Page</base> >>> <generator>MediaWiki 1.17wmf1</generator> >>> <case>first-letter</case> >>> <namespaces> >>> <namespace key="-2" case="first-letter">Media</namespace> >>> <namespace key="-1" case="first-letter">Special</namespace> >>> <namespace key="0" case="first-letter"/> >>> <namespace key="1" case="first-letter">Talk</namespace> >>> <namespace key="2" case="first-letter">User</namespace> >>> <namespace key="3" case="first-letter">User talk</namespace> >>> <namespace key="4" case="first-letter">Wikipedia</namespace> >>> <namespace key="5" case="first-letter">Wikipedia talk</namespace> >>> <namespace key="6" case="first-letter">File</namespace> >>> <namespace key="7" case="first-letter">File talk</namespace> >>> <namespace key="8" case="first-letter">MediaWiki</namespace> >>> <namespace key="9" case="first-letter">MediaWiki talk</namespace> >>> <namespace key="10" case="first-letter">Template</namespace> >>> <namespace key="11" case="first-letter">Template talk</namespace> >>> <namespace key="12" case="first-letter">Help</namespace> >>> <namespace key="13" case="first-letter">Help talk</namespace> >>> <namespace key="14" case="first-letter">Category</namespace> >>> <namespace key="15" case="first-letter">Category talk</namespace> >>> <namespace key="100" case="first-letter">Portal</namespace> >>> <namespace key="101" case="first-letter">Portal talk</namespace> >>> <namespace key="108" case="first-letter">Book</namespace> >>> <namespace key="109" case="first-letter">Book talk</namespace> >>> </namespaces> >>> </siteinfo> >>> >>> >>> >>> Thanks >>> >>> Erol Akarsu >>> >>> >> _______________________________________________ >> BaseX-Talk mailing list >> BaseX-Talk(a)mailman.uni-konstanz.de >> https://mailman.uni-konstanz.de/mailman/listinfo/basex-talk >> >> >> >

1 0

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

BaseX-Talk