[
https://issues.apache.org/jira/browse/SOLR-2438?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13147657#comment-13147657
]
Erick Erickson commented on SOLR-2438:
--------------------------------------
I'd like to nudge this one forward, this has always bugged me and we spend a
lot of time on the user's lists etc. explaining this. Plus, this is a nice
simple patch that I can understand :).
So, I've assigned it to myself and I'd like to carry it to resolution, and for
that I'd like any comments. As far as SOLR-219 is concerned, this seems like a
more targeted fix as Peter mentioned. Does the 80/20 rule apply here? Can we
consider this a step towards a full resolution but "good enough for now"? Or
would introducing a parameter into the schema file be harder to undo later?
This approach seems to put the whole question squarely on the user to determine
if she wants to, while keeping current behavior unless she takes explicit
action which I think is a good thing.
> 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
> Attachments: 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]
