[
https://issues.apache.org/jira/browse/LUCENE-5504?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tim Allison updated LUCENE-5504:
--------------------------------
Attachment: LUCENE-5504_draft.patch
> Move analysis of multiterms into QueryParserBase
> ------------------------------------------------
>
> Key: LUCENE-5504
> URL: https://issues.apache.org/jira/browse/LUCENE-5504
> Project: Lucene - Core
> Issue Type: Improvement
> Components: core/queryparser
> Affects Versions: 5.0
> Reporter: Tim Allison
> Priority: Minor
> Attachments: LUCENE-5504_draft.patch
>
>
> Thanks to MultitermAwareComponents, multiterm analysis works elegantly in
> Solr. In Lucene, we have:
> QueryParserBase and most descendants:
> 1) can lowercase multiterms
> 2) can analyze rangeterms
> 3) can't analyze: fuzzy, prefix, regex, wildcards
> AnalyzingQueryParser
> 1) allows use of main analyzer (with some regex hackery around
> wildcards...mea culpa) to analyze fuzzy, prefix, wildcards
> 2) does not handle regex terms
> It would be cleaner if we got rid of the lowercasing and special analysis of
> range terms and substituted an init() with two analyzers: a regular analyzer
> and a multiterm analyzer. We'll want to improve javadocs and perhaps add a
> SimpleKeyWordLowerCasingAnalyzer...to make the transition easier.
> If we make this change, we'd clean up the hodgepodge of multiterm analysis
> options (get rid of AnalyzingQueryParser) and add multiterm analysis to
> everything that extends QueryParserBase.
> Draft patch on way.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
