[
https://issues.apache.org/jira/browse/LUCENE-5261?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Muir updated LUCENE-5261:
--------------------------------
Attachment: LUCENE-5261.patch
Simplified patch:
* I removed get/set defaultOperator and slop, restoring these to the QPs (so
less changes there: including no api impact)
* I removed operator enum completely and just use Occur for that.
* instead createFieldQuery just takes Occur and slop as parameters.
* added javadocs
>From the "use directly" side I just added
>createBooleanQuery(String,String,Occur) and
>createPhraseQuery(String,String,int).
I think this is much more intuitive, these parameters are really "per-query"
anyway: they shouldnt be getters/setters on this class. (Thats just brain
damage from our crazy QP).
I think this is ready.
> add simple API to build queries from analysis chain
> ---------------------------------------------------
>
> Key: LUCENE-5261
> URL: https://issues.apache.org/jira/browse/LUCENE-5261
> Project: Lucene - Core
> Issue Type: New Feature
> Reporter: Robert Muir
> Attachments: LUCENE-5261.patch, LUCENE-5261.patch, LUCENE-5261.patch
>
>
> Currently this is pretty crazy stuff.
> Additionally its duplicated in like 3 or 4 places in our codebase (i noticed
> it doing LUCENE-5259)
> We can solve that duplication, and make it easy to simply create queries from
> an analyzer (its been asked on the user list), as well as make it easier to
> build new queryparsers.
--
This message was sent by Atlassian JIRA
(v6.1#6144)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
