[
https://issues.apache.org/jira/browse/SOLR-2438?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13147745#comment-13147745
]
Robert Muir commented on SOLR-2438:
-----------------------------------
{quote}
While an optional analysis chain to be used for prefix queries, etc, would be
powerful in some ways, it's not very user friendly and makes the schema harder
to read if we add it for all our fields. We should be able to figure out the
right thing to do in pretty much all cases when our filters are used (i.e. some
filters should be run on a prefix and some shouldn't).
{quote}
I agree with this actually... but it kinda sucks from the plugin perspective.
Can we have both? E.g. we have a pluggable chain, you can declare your own, but
the default is 'AutoAnalyzerFactory' or something like that, which is a factory
that deduces it from the query chain (e.g. for this i would say look for
accent-folding and lowercase and declare success, if you want anything else go
configure your own chain).
Then the schema file wouldn't be messy either.
> 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
