[
https://issues.apache.org/jira/browse/SOLR-2438?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13157222#comment-13157222
]
Yonik Seeley commented on SOLR-2438:
------------------------------------
Let's iterate on this in trunk a while before we backport to 3x.
It's always good when we can avoid configuration, and I think that's the case
here.
First of all, the name "legacyMultiTerm" just begs the question "with respect
to what?".
Second, things would only be non-back compatible if someone were using things
incorrectly (i.e. a query of myfield:Foo when myfield contains a lowecase
filter). It really doesn't seem like we need a "legacyMultiTerm" flag or a
lucene match version for this.
I'll work up a patch to make the analysis a bit more flexible too.
> Case Insensitive Search for Wildcard Queries
> --------------------------------------------
>
> Key: SOLR-2438
> URL: https://issues.apache.org/jira/browse/SOLR-2438
> Project: Solr
> Issue Type: Improvement
> Reporter: Peter Sturge
> Assignee: Erick Erickson
> Attachments: SOLR-2438-3x.patch, SOLR-2438.patch, SOLR-2438.patch,
> SOLR-2438.patch, SOLR-2438.patch, SOLR-2438.patch, SOLR-2438.patch
>
>
> This patch adds support to allow case-insensitive queries on wildcard
> searches for configured TextField field types.
> This patch extends the excellent work done Yonik and Michael in SOLR-219.
> The approach here is different enough (imho) to warrant a separate JIRA issue.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
