One may want to implement a full text index on several different index patterns. e.g. specify an index on some element and an index on some attribute, Would your implementation handle that case?
Yes although right now it's concatenating all the text that matches a particular pattern ([EMAIL PROTECTED]) within a document together and it returns the whole document in the case of a match. I'm changing that behaviour right now :)
Just out of curiosity, does your implementation support the existing standard XPath approach to searching? What sort of analyzer are you using? Did you decide to allow users to specify the analyzer somehow?
You get to specify the Lucene analyzer when you create the index via an additional 'analyzer' attribute.
At the moment I'm not doing XPath search syntax. Searching looks like this:
String query = "some text to find";
TextQueryService tqs =
(TextQueryService) col.getService("TextQueryService", "1.0");
resultSet = tqs.query(query);I'm open to suggestions for improvements / alternatives :)
-- Andy Armstrong, Tagish
