[
https://issues.apache.org/jira/browse/SOLR-2438?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yonik Seeley updated SOLR-2438:
-------------------------------
Attachment: SOLR-2438.patch
Here's a patch with quite a few changes:
- fixed cases that were lowercasing the terms when they shouldn't be
- moved the multiTermAnalyzer methods up to TextField. This strategy isn't
general enough to be used by other field types (think prefix query on a numeric
field, etc)
- added an interface, MultiTermAwareComponent, that can allow a factory to
return another factory (or itself)
- removed legacy_multiTerm... if someone wants that, they can directly
configure a keyword tokenizer.
- made TextField.getRangeQuery() fully functional
- use KeywordTokenizer by default in the MultiTermAnalyzer
- removed from the example schema... this should work for 99% of people and
only expert users should care (and it could confuse new users about when they
need to define a custom multiTermAnalyzer)
- other minor improvements such as not looking up the fieldType twice all the
time in SolrQueryParser
- SOLR-1982 related - don't introspect all fieldTypes for every query parser
instantiation... do it per-field only as required. Also, don't allow wildcard
behavior of one field affect another.
- added some new tests to catch certain cases, fixed some other test cases. A
few more tests might be desirable.
> 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
> Fix For: 3.6, 4.0
>
> Attachments: SOLR-2438-3x.patch, SOLR-2438.patch, SOLR-2438.patch,
> SOLR-2438.patch, SOLR-2438.patch, SOLR-2438.patch, SOLR-2438.patch,
> SOLR-2438.patch, SOLR-2438.patch, SOLR-2438_3x.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]
