[
https://issues.apache.org/jira/browse/LUCENE-5620?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13975300#comment-13975300
]
Mike Sokolov edited comment on LUCENE-5620 at 4/20/14 10:11 PM:
----------------------------------------------------------------
Well, nested is probably not a real use case, but it could certainly happen.
In my test I tried:
preserve, lower-case, preserve, ascii-fold, restore, restore
which gives "test", "tést", "Tést“ for input of "Tést"
why you would want to do this I have no idea
Possibly a use case is preserve, lower-case, preserve, kstem, restore, restore
? Since kstem can only handle lower-case terms, although it would work fine the
other way.
was (Author: sokolov):
Well, nested is probably not a real use case, but it could certainly happen.
In my test I tried:
preserve, lower-case, preserve, ascii-fold, restore, restore
which gives "test", "tést", "Tést“ for input of "Tést"
why you would want to do this I have no idea
> 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, 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]
