lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Landon Cox" <>
Subject RE: Adding a TermExpansionQuery
Date Wed, 15 May 2002 14:54:27 GMT

Basic question of the ilk: exploring assumptions -

Why would Thesaurus/Expanded Terms be something 'stored' by Lucene at all?
Why wouldn't it be something provided by the application to a query that
accepted Thesaurus terms?  In other words, it seems like this functionality
can be built on what's there today - maybe some convenience classes that
accept the Thesaurus to build out the query string, but other than that, I
don't really see a need to change anything to accomodate this.

I can imagine different applications needing different Thesauruses but
having to use the same index. Unless the 'stored' Thesaurus was somehow
indexed by application name or even application instance or alternatively
marked as such in a properties file, all applications might have to live
with the same Thesaurus.

Seems easier and more flexible, with no change to Lucene required (except
convenience classes for query building if desired), to have the application
do the storing/providing.


To unsubscribe, e-mail:   <>
For additional commands, e-mail: <>

View raw message