I assume your indexer only indexes "whole words" (perhps with stemming) and therefore would not be useful in assisting evaluation of the "contains" or "ends-with" functions (as a substring index would be useful for)?
e.g.
if the text was: "some words"
contains("some words", "wor") would return true,
but if you indexed only whole words,
you would not find "wor" in the index
therefore the index would not be useful
for assisting in evaluation of the contains function.-Terry
Andy Armstrong wrote:
I've written a full text indexer that builds a Lucene index. That all seems to work fine. Now the hard part: what should the API be for querying the index? I can't find a spec for XPath full text queries although there is this document:
http://www.w3.org/TR/2003/WD-xquery-full-text-requirements-20030502/
which sets out a few requirements. Any thoughts?
