[
https://issues.apache.org/jira/browse/LUCENE-5470?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13911787#comment-13911787
]
Robert Muir commented on LUCENE-5470:
-------------------------------------
Can we just analyze multiterm queries without trying to parse around wildcards
or what not? This is basically what solr is doing today. I think trying to
interpret the syntax is a bit too funky and error-prone, and its better if
someone wants "magic" to have that in their QP itself.
I think its assumed you will use a different analyzer for this stuff (e.g. with
keywordtokenizer) than you normally would, so this syntax is no problem really.
This is why for example, QueryParserBase is specifically setup for you to
supply that simpler, different analyzer:
{code}
protected BytesRef analyzeMultitermTerm(String field, String part, Analyzer
analyzerIn) {
{code}
> Refactoring multiterm analysis
> ------------------------------
>
> Key: LUCENE-5470
> URL: https://issues.apache.org/jira/browse/LUCENE-5470
> Project: Lucene - Core
> Issue Type: Bug
> Components: core/queryparser
> Affects Versions: 5.0
> Reporter: Tim Allison
> Priority: Minor
> Attachments: LUCENE-5470.patch
>
>
> There are currently three methods to analyze multiterms in Lucene and Solr:
> 1) QueryParserBase
> 2) AnalyzingQueryParser
> 3) TextField (Solr)
> The code in QueryParserBase and in TextField do not consume the tokenstream
> if more than one token is generated by the analyzer. (Admittedly, thanks to
> the magic of MultitermAwareComponents in Solr, this type of exception
> probably never happens and the unconsumed stream problem is probably
> non-existent in Solr.)
> I propose consolidating the multiterm analysis code into one place:
> QueryBuilder in Lucene core.
> This is part of a refactoring that will also help reduce duplication of code
> with LUCENE-5205.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
