Mike Matrigali wrote: > Dan, do you have a vision on how such an integration would work.
Not at any detailed level, I just believe it would *not* make sense for the Derby project to re-invent text indexing and searching when there's a well tested fully functioning Java text search engine as a Apache project. I do remember I could get the another similar text engine hacked into Cloudscape and supporting queries with ranking in a few hours. If I had to invent text indexing as well it would have taken years. > I understand using the libraries to process the CONTAINS function. You > mentioned you tried some prototyping, did you put the actual index into > an existing derby table or did you store the index separate? In that prototype I just stored the index in separate files, no transactional support. > > My questions are: > > 1) would actual index be stored in a derby style page container, which > would somehow map the index structure that lucene expected? Does the > lucene architecture map to a row locked multi-user environment? http://wiki.apache.org/jakarta-lucene/LuceneFAQ#head-acc3c9bd1758a9794b93cd1a028cf95b0fddaf86 > 2) Would there be work in the optimizer to get it to recognize that > there was an index that helped with the CONTAINS() function. Is this > the sort of work needed for DERBY-455 creation of indexes on expressions? Possibly. Dan.
