Mailing-List: contact java-user-help@lucene.apache.org; run by ezmlm
Precedence: bulk
Reply-To: java-user@lucene.apache.org
MIME-Version: 1.0
In-Reply-To: <CAL8Pwkbqi63TENuLs2jRJBO0mFNzzkQdquc9xBv26JrALF1CXA@mail.gmail.com>
References: <CAC9XQeuU+4=W9VNKrgJYWQqxQJSXNpgb_o8unMcgc1itX6S5OQ@mail.gmail.com>
 <CAL8Pwkbqi63TENuLs2jRJBO0mFNzzkQdquc9xBv26JrALF1CXA@mail.gmail.com>
From: hariram ravichandran <hariramravichandar@gmail.com>
Date: Wed, 30 Nov 2016 17:59:13 +0530
Message-ID: <CAC9XQet0+dpf7QBYOVUq7f05r1hHXpL=cVxXUD35AvZoaregsg@mail.gmail.com>
Subject: Re: Query expansion
To: Michael McCandless <lucene@mikemccandless.com>
Cc: Lucene Users <java-user@lucene.apache.org>
Content-Type: multipart/alternative; boundary=94eb2c09216c40a0f3054283dadf
archived-at: Wed, 30 Nov 2016 12:29:20 -0000

--94eb2c09216c40a0f3054283dadf
Content-Type: text/plain; charset=UTF-8

I am overriding getFieldQuery(String field, String fieldText,boolean
quoted). And in case of phrase query,

getFieldQuery(String field, String queryText, int slop) will be called.


And prefix query will not be my use case. So, we can ignore prefix query.


Assume this is my only case. Sequence of words (apple orange mango) as
input, and i need result for (apple~ orange~  mango~).

And I use default conjunction operator as AND (parser.setDefaultOperator(
QueryParser.Operator.AND)) for providing better relevance in results.


That method works as I expected. Is there any drawbacks of using this?


And is there any better method to expand query like this?


On Wed, Nov 30, 2016 at 4:37 AM, Michael McCandless <
lucene@mikemccandless.com> wrote:

> This is likely tricky to do correctly.
>
> E.g., MultiFieldQueryParser.getFieldQuery is invoked on whole chunks
> of text.  If you search for:
>
>   apple orange
>
> I suspect it won't do what you want, since the whole string "apple
> orange" is passed to getFieldQuery.
>
> How do you want to handle e.g. a phrase query (user types "apple
> orange", with the double quotes)?  Or a prefix query (app*)?
>
> Maybe you could instead override newTermQuery?  In the example above
> it would be invoked twice, once for apple and once for orange.
>
> Finally, all this being said, making everything fuzzy is likely a big
> performance hit and often poor results (massive recall, poor
> precision) to the user!
>
> Mike McCandless
>
> http://blog.mikemccandless.com
>
>
> On Mon, Nov 28, 2016 at 6:24 AM, hariram ravichandran
> <hariramravichandar@gmail.com> wrote:
> > I need to perform *fuzzy search* for the whole search term. I
> > extended MultiFieldQueryParser and overridden getFieldQuery()
> >
> >
> > protected Query getFieldQuery(String field, String fieldText,boolean
> > quoted) throws ParseException{
> >            return *super.getFuzzyQuery(field,fieldText,3.0f);
> > //constructing fuzzy query*
> > }
> >
> > For example, If i give search term as "(apple AND orange) OR (mango)",
> the
> > query should be expanded as "(apple~ AND orange~) OR (mango~)".
> >
> > I need to search in multiple fields and also i need to implement this
> > without affecting any of the lucene features. Is there any other simple
> way?
>

--94eb2c09216c40a0f3054283dadf--