[jira] [Resolved] (LUCENE-6464) Allow possibility to group contexts in AnalyzingInfixSuggester.loockup()

["Michael McCandless (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/LUCENE-6464?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Michael McCandless resolved LUCENE-6464.
----------------------------------------
       Resolution: Fixed
    Fix Version/s: 5.2
                   Trunk

Thanks [~arcadius]!

> Allow possibility to group contexts in AnalyzingInfixSuggester.loockup()
> ------------------------------------------------------------------------
>
>                 Key: LUCENE-6464
>                 URL: https://issues.apache.org/jira/browse/LUCENE-6464
>             Project: Lucene - Core
>          Issue Type: Improvement
>    Affects Versions: 5.1
>            Reporter: Arcadius Ahouansou
>             Fix For: Trunk, 5.2
>
>         Attachments: LUCENE-6464.patch
>
>
> This is an enhancement to LUCENE-6050 
> LUCENE-6050 added
> {code}
> lookup(CharSequence key, Map<BytesRef, BooleanClause.Occur> contextInfo, int num, boolean allTermsRequired, boolean doHighlight)
> {code}
> which allowed to do something like
> (A OR B AND C OR D ...)
> In our use-case, we realise that we need grouping i.e
> (A OR B) AND (C OR D) AND (...)
> In other words, we need the intersection of multiple contexts.
> The attached patch allows to pass in a varargs of map, each one representing the each group. Looks a bit heavy IMHO.
> This is an initial patch.
> The question to [~mikemccand] and [~janechang] is:
> is it better to expose a FilteredQuery/Query and let the user build their own query instead of passing a map?
> Exposing a filteredQuery will probably give the best flexibility to the end-users.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org