would be to use it to build a substring index useful for
assisting in evaluation of the "contains" and "ends-with"
operators.
Perhaps index all 3 character substrings and modify XPathQueryResolver and friends to look for/use such an index when it encounters contains(something, AString) and AString.length() >= 3. (Ditto for "ends-with" - remember that indexed searches do not have to produce the exact answer - just narrow the number of documents that need "ordinary" XPath evaluation at the end).
-Terry
Andy Armstrong wrote:
Vadim Gritsenko wrote:
Which are made available to the client via QueryService: XPathQueryServiceImpl XUpdateQueryServiceImpl
Would it make sense to add FullTextQueryServiceImpl, or LuceneQueryServiceImpl, and use Lucene's query syntax to access lucene indexer?
I certainly think it'd be nice to have that as an option even if I also make it handle XPath queries. That way you'd have access to Lucene's searching operators.
