[
https://issues.apache.org/jira/browse/SOLR-2438?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Erick Erickson updated SOLR-2438:
---------------------------------
Attachment: SOLR-2438.patch
I think this patch is ready for scrutiny. Tests run successfully.
I have yet to do several things:
1> update README
2> add an example to example/schema.xml
3> this is going to take a writeup on the Wiki I think, explaining that there's
another (optional) section to a <fieldType>. Any suggestions where that should
go?
Originally, I'd hoped to back-port it to 3.5, but the more I look at it the
more I'd like it to bake a while before being officially released and target
3.6 instead for the back-port. Can one back-port something like this after the
first RC is cut or is it better to wait until after the release? I can always
commit this to trunk and open another JIRA to backport after 3.5 is released.
> 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, 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]
