Return-Path: Delivered-To: apmail-lucene-java-user-archive@www.apache.org Received: (qmail 78251 invoked from network); 29 Nov 2008 07:04:49 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 29 Nov 2008 07:04:49 -0000 Received: (qmail 94320 invoked by uid 500); 29 Nov 2008 07:04:53 -0000 Delivered-To: apmail-lucene-java-user-archive@lucene.apache.org Received: (qmail 94288 invoked by uid 500); 29 Nov 2008 07:04:53 -0000 Mailing-List: contact java-user-help@lucene.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: java-user@lucene.apache.org Delivered-To: mailing list java-user@lucene.apache.org Received: (qmail 94275 invoked by uid 99); 29 Nov 2008 07:04:53 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 28 Nov 2008 23:04:53 -0800 X-ASF-Spam-Status: No, hits=2.2 required=10.0 tests=HTML_MESSAGE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: local policy) Received: from [216.252.110.215] (HELO web56206.mail.re3.yahoo.com) (216.252.110.215) by apache.org (qpsmtpd/0.29) with SMTP; Sat, 29 Nov 2008 07:03:26 +0000 Received: (qmail 42923 invoked by uid 60001); 29 Nov 2008 07:03:11 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=X-YMail-OSG:Received:X-Mailer:References:Date:From:Subject:To:MIME-Version:Content-Type:Message-ID; b=PszvvztaSBQAo+TOtXyrpWiCY3rXzUMCG6an0SD6xJGz8mWYpTjs98weYLvQuiZjZ7fwoiukWvfBfaIsKfTp39wk8WuNb/EsfVxJsSMOJyq6v6PGcQPta4ff4pmpRtbM03n/wZXPCXWYbgCBxYNaf4LF644R0Bc4CpFS/jzOm1A=; X-YMail-OSG: drOlHmQVM1nsAgqBZTtnr3zlOpvmqu2M6quVoSa3cyx5XYss8tuZzG71HJ93iBprUF.xCGvJpPGQBExV2JbB45eWJigM84vMG.h68YjR.vkTPVi2Gdo.I0YhKJMJabE_mGy2isV0nPz5KvtdwmQzYU60JwviJgnUvR9T8P36Xwo_f4Io2qE5WuBRDq9u Received: from [91.98.7.77] by web56206.mail.re3.yahoo.com via HTTP; Fri, 28 Nov 2008 23:03:10 PST X-Mailer: YahooMailRC/1155.32 YahooMailWebService/0.7.260.1 References: <986640.21817.qm@web56206.mail.re3.yahoo.com> <76df56980811281638g6736daaegefbd945712a33fbf@mail.gmail.com> Date: Fri, 28 Nov 2008 23:03:10 -0800 (PST) From: Amir Hossein Jadidinejad Subject: Re: Controlled Indexing -New Feature To: java-user@lucene.apache.org MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="0-1178313736-1227942190=:42466" Message-ID: <171262.42466.qm@web56206.mail.re3.yahoo.com> X-Virus-Checked: Checked by ClamAV on apache.org --0-1178313736-1227942190=:42466 Content-Type: text/plain; charset=us-ascii Yes, It's good to filter words but suppose that my controlled vocabulary contains synonyms and etc.Exactly, I want to supervise on indexing process. Thank you very much. ________________________________ From: German Kondolf To: java-user@lucene.apache.org Sent: Friday, November 28, 2008 7:38:34 PM Subject: Re: Controlled Indexing -New Feature You could use a "reverse" stop-word filter. The straight "StopFilter" actually removes the keywords that match with a given Set of words, you could do the reverse logic of that an remove ALL keywords that doesn't match that Set. Take a look at StopFilter and StandardAnalyzer ;) On Fri, Nov 28, 2008 at 4:38 PM, Amir Hossein Jadidinejad < amir.jadidi@yahoo.com> wrote: > Hi, > I'm going to index some documents only with known phrases. Let me describe: > Suppose that I have a controlled vocabulary(a list of some known > phrases/words). I intend to > index ONLY these phrases within my documents and have a retrieval model > (for example simple VS-TF.IDF). In way, each index item is one of the > predefined > phrase. > Is it possible to handle this situation with Lucene? > What is the best way?! > Greatly appreciate any comments or answers. > Kind regards, > > > > --0-1178313736-1227942190=:42466--