Return-Path: Delivered-To: apmail-jakarta-lucene-dev-archive@apache.org Received: (qmail 91184 invoked from network); 15 May 2002 14:55:09 -0000 Received: from unknown (HELO nagoya.betaversion.org) (192.18.49.131) by daedalus.apache.org with SMTP; 15 May 2002 14:55:09 -0000 Received: (qmail 11662 invoked by uid 97); 15 May 2002 14:55:10 -0000 Delivered-To: qmlist-jakarta-archive-lucene-dev@jakarta.apache.org Received: (qmail 11614 invoked by uid 97); 15 May 2002 14:55:08 -0000 Mailing-List: contact lucene-dev-help@jakarta.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Help: List-Post: List-Id: "Lucene Developers List" Reply-To: "Lucene Developers List" Delivered-To: mailing list lucene-dev@jakarta.apache.org Received: (qmail 11589 invoked by uid 98); 15 May 2002 14:55:07 -0000 X-Antivirus: nagoya (v4198 created Apr 24 2002) From: "Landon Cox" To: "Lucene Developers List" Subject: RE: Adding a TermExpansionQuery Date: Wed, 15 May 2002 08:54:27 -0600 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0) In-Reply-To: Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.00.3018.1300 X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N 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. Landon -- To unsubscribe, e-mail: For additional commands, e-mail: