Great idea! I would suggest the following considerations: - this should be implemented as an interface that can support multiple implementations (such as something based on a simple lookup table and also something based on a wordNet-style synonim database) - different implementations might be probably be used for the same index either at the same time or at different times - for those using Lucene primarialy as an API, the implementations is best provided programmatically when creating a Searcher, I think. - for those using Lucene as an application, perhaps the application framework (such as the one people are working on in the sandbox) can take care of finding and instantiating the right implementation.
Good luck! Dmitry. Peter Carlson wrote: >Hi, > >I was thinking of adding a TermExpansionQuery, basically if it finds the >term in a lookup table, then it would also include an associated set of >terms. > >For example, if the search term was "pet" it might also add "dog", "cat", >"bird" > >The issue that I am having is were to store the terms and how to have Lucene >know where that information is stored. > >Should there be a Lucene properties file? Should this be another type of >file in the Lucene index folder? > >Suggestions would be appreciated. > >--Peter > > >-- >To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> >For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> > > -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
