[
https://issues.apache.org/jira/browse/LUCENE-7355?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15353173#comment-15353173
]
Adrien Grand commented on LUCENE-7355:
--------------------------------------
This sounded appealing so I gave it a try but I hit a couple problems:
- some analyzers need to apply char filters too, so we cannot expect to have a
String in all cases we need some sort of KeywordTokenizer
- some consumers need to get the binary representation of terms, which depends
on the AttributeFactory (LUCENE-4176). So maybe we should return a TokenStream
rather than a String an let consumers decide whether they want to add a
CharTermAttribute or a TermToBytesRefAttribute. Is there a better option?
> Leverage MultiTermAwareComponent in query parsers
> -------------------------------------------------
>
> Key: LUCENE-7355
> URL: https://issues.apache.org/jira/browse/LUCENE-7355
> Project: Lucene - Core
> Issue Type: Improvement
> Reporter: Adrien Grand
> Priority: Minor
> Attachments: LUCENE-7355.patch, LUCENE-7355.patch
>
>
> MultiTermAwareComponent is designed to make it possible to do the right thing
> in query parsers when in comes to analysis of multi-term queries. However,
> since query parsers just take an analyzer and since analyzers do not
> propagate the information about what to do for multi-term analysis, query
> parsers cannot do the right thing out of the box.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
