[ 
https://issues.apache.org/jira/browse/SOLR-757?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Erick Erickson resolved SOLR-757.
---------------------------------

       Resolution: Fixed
    Fix Version/s:     (was: 3.5)
                   3.6
         Assignee: Erick Erickson

I'm pretty sure this is taken care of by SOLR-2438, so marking closed.
                
> SolrQueryParser should support escaping of characters in lieu of analysis for 
> prefix & wildcard & fuzzy searches.
> -----------------------------------------------------------------------------------------------------------------
>
>                 Key: SOLR-757
>                 URL: https://issues.apache.org/jira/browse/SOLR-757
>             Project: Solr
>          Issue Type: Improvement
>          Components: search
>    Affects Versions: 1.3
>            Reporter: David Smiley
>            Assignee: Erick Erickson
>             Fix For: 3.6, 4.0
>
>         Attachments: SolrQueryParser_wildcardescape.patch
>
>
> In Lucene and Solr, query words that are prefix or wildcard or fuzzy do not 
> go through analyzer processing.  This is for well known understood reasons.  
> However, for my data for a field I might want certain processing to occur.  
> Lowercasing has already been identified in SOLR-219.  Another which I address 
> in the attached patch file is the ability to remove characters that meet a 
> supplied regular expression.  I've implemented this as part of 
> SolrQueryParser but there should probably be a more thorough plan such as an 
> analyzer chain expressly for the purpose of being applied to prefix, 
> wildcard, and fuzzy queries.

--
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]

Reply via email to