[
https://issues.apache.org/jira/browse/LUCENE-7692?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15865082#comment-15865082
]
Erick Erickson commented on LUCENE-7692:
----------------------------------------
The basic rule is that as long as the filter doesn't output more than one
token per input token, making it MultiTermAware is appropriate.
There was never an attempt to do an exhaustive analysis of _all_ the filters
that qualified. Frankly, my motivation was that explaining over and over again
that "wildcard searches are case sensitive because...." got really tiring so
just fixing that use-case was enough to get us going, the rest was an added
benefit ;)
Since then it's more have been added but mostly whenever someone was motivated
to add another, so please feel free.
> PatternReplaceCharFilterFactory should implement MultiTermAware
> ---------------------------------------------------------------
>
> Key: LUCENE-7692
> URL: https://issues.apache.org/jira/browse/LUCENE-7692
> Project: Lucene - Core
> Issue Type: Improvement
> Reporter: Adrien Grand
> Assignee: Adrien Grand
> Priority: Minor
>
> The multi-term aware marker API is useful to know which analysis components
> to apply when analyzing prefix or wildcard queries. I think
> PatternReplaceCharFilterFactory qualifies?
> For the record, we have MappingCharFilterFactory that does a similar job
> (except that it takes an explicit map of replacements rather than regular
> expressions) and implements MultiTermAware.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
