[
https://issues.apache.org/jira/browse/LUCENE-9386?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17154557#comment-17154557
]
ASF subversion and git services commented on LUCENE-9386:
---------------------------------------------------------
Commit fec5d49112ab23ce67792ddc821b1addcc8eea5d in lucene-solr's branch
refs/heads/branch_8x from markharwood
[ https://gitbox.apache.org/repos/asf?p=lucene-solr.git;h=fec5d49 ]
LUCENE-9386 add case insensitive RegExp matching option. (#1659)
Backport of 887fe4c83d4114c6238265ca7f05aa491525af9d
> RegExpQuery - add case insensitive matching option
> --------------------------------------------------
>
> Key: LUCENE-9386
> URL: https://issues.apache.org/jira/browse/LUCENE-9386
> Project: Lucene - Core
> Issue Type: Improvement
> Components: core/search
> Reporter: Mark Harwood
> Priority: Minor
> Time Spent: 10m
> Remaining Estimate: 0h
>
> In searches sometimes case sensitivity is important and sometimes not.
> However, users don't want to have to index two versions of their data
> (lowercased and original) in order to service both case sensitive and case
> insensitive queries. To get around this users have been commonly seen to take
> a user query e.g. `powershell.exe` and search for it with the regex
> `[Pp][Oo][Ww][Ee][Rr][Ss][Hh][Ee][Ll][Ll]\.[Ee][Xx][Ee]`.
> The proposal is that we add an extra "case insensitive" option to the RegExp
> query flags to automatically do this sort of expansion when we create
> Automatons.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]