Return-Path: X-Original-To: apmail-lucene-java-user-archive@www.apache.org Delivered-To: apmail-lucene-java-user-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 2CB1710518 for ; Wed, 21 Aug 2013 07:52:02 +0000 (UTC) Received: (qmail 35235 invoked by uid 500); 21 Aug 2013 07:51:59 -0000 Delivered-To: apmail-lucene-java-user-archive@lucene.apache.org Received: (qmail 34424 invoked by uid 500); 21 Aug 2013 07:51:58 -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 33543 invoked by uid 99); 21 Aug 2013 07:51:55 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 21 Aug 2013 07:51:55 +0000 X-ASF-Spam-Status: No, hits=-0.0 required=5.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: local policy) Received: from [116.50.78.85] (HELO mta3.rancoretech.com) (116.50.78.85) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 21 Aug 2013 07:51:50 +0000 X-IronPort-AV: E=Sophos;i="4.89,926,1367951400"; d="scan'208";a="59903566" Received: from unknown (HELO outpostfix01.ril.com) ([10.66.8.167]) by gwsmtp011.ril.com with ESMTP; 21 Aug 2013 13:21:22 +0530 Received: from rdmail.rancoretech.com (unknown [10.22.140.196]) by outpostfix01.ril.com (Postfix) with SMTP id D486B12FBCD for ; Wed, 21 Aug 2013 13:21:23 +0530 (IST) Received: from localhost (localhost.localdomain [127.0.0.1]) by rdmail.rancoretech.com (Postfix) with ESMTP id CAE714A8883D for ; Wed, 21 Aug 2013 13:21:23 +0530 (IST) X-Virus-Scanned: amavisd-new at rancoretech.com Received: from rdmail.rancoretech.com ([127.0.0.1]) by localhost (rdmail.rancoretech.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id w3KT4g00pyVY for ; Wed, 21 Aug 2013 13:21:23 +0530 (IST) Received: from [10.49.16.89] (unknown [10.49.16.89]) by rdmail.rancoretech.com (Postfix) with ESMTPSA id B4CFF4A8882B for ; Wed, 21 Aug 2013 13:21:23 +0530 (IST) Message-ID: <5214717B.4020007@rancoretech.com> Date: Wed, 21 Aug 2013 13:21:23 +0530 From: Ankit Murarka User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.1.5) Gecko/20091204 Thunderbird/3.0 MIME-Version: 1.0 To: java-user@lucene.apache.org Subject: Re: Boolean Query when indexing each line as a document. References: <5209E6C3.2000609@rancoretech.com> <520A06CE.1080305@rancoretech.com> <520B8B36.4090505@rancoretech.com> <520B9434.3000407@rancoretech.com> <520B9859.10206@rancoretech.com> <520F2A21.9040905@rancoretech.com> <5211B87D.7000201@rancoretech.com> <5211C1FE.2080801@robertoragusa.it> <52146056.1020406@rancoretech.com> <52146B8C.8020507@robertoragusa.it> In-Reply-To: <52146B8C.8020507@robertoragusa.it> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org Yeah..I eventually DID THIS.... Just a small question : Knowing that BooleanQuery/PrefixQuery/WildCardQuery might also run fine even if I index the complete document as opposed to doing it Line by Line. Shouldn't I do it this way rather than indexing each line for Boolean/Prefix/Wildcard also. ? What might be the impact on performance. What might be possible pitfalls.. Also Final part is showing user the content above and below the given query to search. Will this be achieveable if I index document by document for Boolean/Prefix/Wildcard... Kindly advice... On 8/21/2013 12:56 PM, Roberto Ragusa wrote: > On 08/21/2013 08:38 AM, Ankit Murarka wrote: > >> Hello. >> I tried with >> >> doc.add(new Field("contents",line,Field.Store.YES,Field.Index.ANALYZED)); >> >> The BooleanQuery/PrefixMatch/WildCard all started Running fine.. >> >> But it broke the Existing code for Phrase Suggestion/InfixSuggester. Now these suggesters are returning Word suggestion instead of Phrase Suggestion which is not serving any purpose. >> >> THIS IS NOT DESIRABLE.. >> >> My PhraseSuggestion/InfixSuggestion etc. is now not working fine. Please guide.. This is complete blocker. >> > I do not know how PhraseSuggestion/InfixSuggestion work, but, assuming > there is no better solution, you could try indexing both a Field and a StringField > (with different field names) and using the first for searching and the second > for suggestions. > > -- Regards Ankit Murarka "What lies behind us and what lies before us are tiny matters compared with what lies within us" --------------------------------------------------------------------- To unsubscribe, e-mail: java-user-unsubscribe@lucene.apache.org For additional commands, e-mail: java-user-help@lucene.apache.org