From: Patrick S. <pat...@zi...> - 2010-07-12 09:08:07
|
Hi Joe, I use the following settings: conf.xml <db-connection cacheSize="3000M" collectionCache="128M" database="native" files="webapp/WEB-INF/data" pageSize="4096" nodesBuffer="-1"> eXist-settings.sh: set_client_java_options() { if [ -z "${CLIENT_JAVA_OPTIONS}" ]; then CLIENT_JAVA_OPTIONS="-Xms128m -Xmx8000m -Dfile.encoding=UTF-8"; } set_java_options() { if [ -z "${JAVA_OPTIONS}" ]; then JAVA_OPTIONS="-Xms128m -Xmx8000m -Dfile.encoding=UTF-8"; } > This might take you on the wrong track, but you could try adding a > Lucene index on @id / @value. Even though we usually think of using > Lucene for fulltext search, it might be worth trying out the > whitespace analyzer -- see http://exist-db.org/lucene.html#N102F8. > Given all of the weird characters in your @value example, you should > probably construct your query as XML rather than using the lucene > search query parser, which could get thrown off -- see > http://exist-db.org/lucene.html#N10352. It'd be interesting to know > how this works compared to the range indexes. I created an lucene index on @value: <lucene> <analyzer class="org.apache.lucene.analysis.standard.StandardAnalyzer"/> <analyzer id="ws" class="org.apache.lucene.analysis.WhitespaceAnalyzer"/> <text qname="@value" analyzer="ws"/> </lucene> and used the query: let $query := <query> <term>Cc1c2c(ncn(c2=O)C)sc1C(=O)NCc1ccc(cc1)CN1CCOCC1</term> </query> for $i in collection("tuscreen")//*[ft:query(@value, $query)] return $i Unfortunately it doesn't return a result? But the query still takes: 12 Jul 2010 11:05:44,920 [P1-9] DEBUG (XQuery.java [execute]:231) - Execution took 5.456 ms Patrick |