Hello Timo Boehme,
I had the same effect. I imported a lot of documents and after this I created the index. The xpath search is very slow (not better without index). best recards Thomas Rupp > Now I've created a new collection, then I add an indexer for an > attribute.. > > then i add 500.000 test documents which have a counter for the > attributevalue > > 1,2GB Data (500MB for the index) > > now the search needs 120ms, that's fast I think. > > great!!! > > Dirk Bromberg > > running xindice 1.0 ,1GHZ AMD, IDE HDD > > > > > Timo Boehme wrote: > > >Hi, > > > >>My question: > >>if i create an index with: > >>xindiceadmin add_indexer -c /db/test -n idIndexer -p id > >>(I'm seraching with this xpath: "//test/id["2447734"]" ) > >>I'm wondering creating xindexer takes no time. > >>After creating this indexer the search is not faster , why ?? or must I > >>create the indexer before adding the documents ?? > >> > > > >Is id an attribute or an element? It looks like an element to me. If id > is > >an attribute you have to add '@' beforehand. > > > >Nevertheless I tried to do something similar some time ago but got an > >NullPointerExecption when creating the index. I wrote in with the > >following mail: > > > >: I would like to create an index for all foo attributes within my > >: collection. According to the documentation I specified [EMAIL PROTECTED] > >as the > index > >: pattern. However the database server throws NullPointerExceptions for > all > >: documents within the collection during indexing. The exception looks > like > >: > >: DEBUG> java.lang.NullPointerException > >: at > org.apache.xindice.core.indexer.IndexPattern.getMatchLevel(Unknown Source) > >: at > org.apache.xindice.core.indexer.IndexManager$SAXHandler.processEntry(Unknown Source) > >: at > org.apache.xindice.core.indexer.IndexManager$SAXHandler.endElement(Unknown Source) > >: at > org.apache.xindice.xml.sax.SAXEventGenerator.processContainer(Unknown Source) > >: at > org.apache.xindice.xml.sax.SAXEventGenerator.processContainer(Unknown Source) > >: at > org.apache.xindice.xml.sax.SAXEventGenerator.processDocument(Unknown Source) > >: at org.apache.xindice.xml.sax.SAXEventGenerator.start(Unknown > Source) > >: at > org.apache.xindice.core.indexer.IndexManager$SAXHandler.<init>(Unknown Source) > >: at > org.apache.xindice.core.indexer.IndexManager.populateNewIndexers(Unknown Source) > >: at > org.apache.xindice.core.indexer.IndexManager.access$300(Unknown Source) > >: at > org.apache.xindice.core.indexer.IndexManager$AutoIndexer.run(Unknown Source) > >: > >: You can easily reproduce this problem: > >: 1. add a collection testcoll to db > >: 2. add a simple document (e.g. <test>text</test>) to /db/testcoll > >: 3. add index with pattern [EMAIL PROTECTED] to /db/testcoll > >: > >: I got this with Xindice RC1 running on Solaris and on Windows 2000. > > > >I got a reply from Tom Bradford: > > > >: I'll try to get this fixed this evening. It's probably something > >: simple, and the result of stupidity. :) > > > >However I haven't heard anything afterwards and the bug seems to be still > >there. Can somebody please have a look on it? > > > > > > > >Best regards, > >Timo > > > > > >--------------------------------------------------- > > Dipl. Inf. Timo Boehme Phone: +49 341 9732166 > > University of Leipzig Fax: +49 341 9732209 > > Institute of Computer Science, Database Group > > Augustusplatz 10-11, 04109 Leipzig, Germany > > email: [EMAIL PROTECTED] > >--------------------------------------------------- > > > > > > > > > -- GMX - Die Kommunikationsplattform im Internet. http://www.gmx.net
