lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Michael McCandless (JIRA)" <>
Subject [jira] [Commented] (LUCENE-7026) AnalyzingInfixSuggester doesn't support Phrase Queries for contexts
Date Mon, 15 Feb 2016 10:12:18 GMT


Michael McCandless commented on LUCENE-7026:

Are you sharing your own index with the index that {{AnalyzingInfixSuggester}} creates?  I.e.
are you indexing your own context fields directly using your own {{IndexWriter}}?

You are not supposed to do that.  Instead, give {{AnalyzingInfixSuggester}} its own private
index and let it do all indexing into that.

> AnalyzingInfixSuggester doesn't support Phrase Queries for contexts
> -------------------------------------------------------------------
>                 Key: LUCENE-7026
>                 URL:
>             Project: Lucene - Core
>          Issue Type: Bug
>          Components: core/index
>    Affects Versions: 5.3.1
>            Reporter: Kamaldeep Singh
> AnalyzingInfixSuggester uses Term Queries for filtering out the contexts. If the StandardAnalyzer
is used while indexing , since all the contexts are stored as StringField and analyzed , spaces
in them  are removed and words converted to tokens. So contexts having spaces in their terms
can't be queried , And we also can't pass a PhraseQuery as a BooleanQuery to lookup() since
Phrase Queries won't work on string fields where positions of tokens are not stored. 
> Option left is to use a different analyzer while indexing 
> Analyzing Infix Suggester should store contexts as TextField instead of StringField so
they can be queried. 

This message was sent by Atlassian JIRA

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

View raw message