lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Robert Muir (Commented) (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (SOLR-2438) Case Insensitive Search for Wildcard Queries
Date Fri, 18 Nov 2011 01:06:52 GMT

    [ https://issues.apache.org/jira/browse/SOLR-2438?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13152545#comment-13152545
] 

Robert Muir commented on SOLR-2438:
-----------------------------------

This is totally the general approach I wanted to see here!

So then we are only left with the two configuration cases to think about:
1. we have the backwards case where no chain is specified, and we want to provide the behavior
of today. I think the simplest solution is to just use set the analyzer to keywordanalyzer
for that? This might simplify logic as then this 'analyzer' for the field is never non-null,
and QP just always analyzes these queries.
2. we have the 'auto' case where no chain is specified, and we want to do the right thing
automatically. so in that situation I think we always build a chain based off of the users
CharFilter setup + keywordtokenizer + lowercasefilter (if lowercasetokenizer/filter is in
use) + asciifoldingfilter (if its in use). anything more complicated and someone just declares
their own chain.
                
> 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
>
>
> 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-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org


Mime
View raw message