[
https://issues.apache.org/jira/browse/LUCENE-5620?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13974911#comment-13974911
]
Mike Sokolov commented on LUCENE-5620:
--------------------------------------
That's the approach we have been using, but it leads to a larger index and a
proliferation of fields. If you want query-time control over whether to search
case-insensitive, diacritic-insensitive, you have to create four fields, one
for each combination (now it's only two because of LUCENE-5437). I also don't
think this leads to very many other places - what would they be? We have
sometimes wanted to turn stemming on and off as well, but other than that I
don't know which other filters would be likely targets for this kind of
enhancement.
> LowerCaseFilter.preserveOriginal
> --------------------------------
>
> Key: LUCENE-5620
> URL: https://issues.apache.org/jira/browse/LUCENE-5620
> Project: Lucene - Core
> Issue Type: Improvement
> Reporter: Mike Sokolov
> Attachments: LUCENE-5620.patch
>
>
> Following closely the model of LUCENE-5437 (which worked on
> ASCIIFoldingFilter), this patch adds the ability to preserve the original
> token to LowerCaseFilter. This is useful if you want an all-lowercase search
> term to match without regard to case, while search terms with uppercase
> letters match in a case-sensitive manner.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
