[
https://issues.apache.org/jira/browse/SOLR-2438?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13147767#comment-13147767
]
Erick Erickson commented on SOLR-2438:
--------------------------------------
I was thinking about trying to explain another type of analyzer a-la SOLR-219.
And maybe a fourth type if SOLR-2477 were implemented. And it was giving me a
headache, especially when that would require the users to understand what is
arguably an expert option before they could handle the 80% case...
So what about making this bug deal with the accents and case folding as Robert
suggests and leave the pluggable stuff for 219 if anyone wants to take it on?
And if we do it that way, should we make the user specify a per-field flag
(suggestions welcome) or *really* make this the default and change the current
behavior? This latter seems like a bad idea for 3.x, but possibly make the
default to auto-detect in trunk?
> 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.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: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
