[
https://issues.apache.org/jira/browse/SOLR-2438?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13157251#comment-13157251
]
Erick Erickson commented on SOLR-2438:
--------------------------------------
Too late, I checked all this in before I saw your comment, including into 3.6.
Yeah, legacyMultiTerm is awkward, and I'm pretty confused by the lucene match
version, so anything you want to do there is welcome. what I was trying for was
the capability to
1> keep from changing the behavior on someone installing over an older 3.x
version
2> allow them to keep the old behavior if necessary. I admit I have a hard time
coming up with a use-case here, but at least it *does* allow them to sidestep
the whole process if someone counts on the old behavior.
At root I'm uncomfortable deciding *for* them what's best without a way of
having the user say "no, you dolt, you didn't anticipate *my* use case!".
Anyway, I opened up SOLR-2918
> 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]
