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

Erick Erickson commented on SOLR-2438:
--------------------------------------

Yikes!

How did you "remove the method"? Comment it out and comment out the call to it 
or something else? I'll need to do whatever you did to reproduce it.

And do you expect that this would also be an issue for trunk? As I remember, 
the two implementations are pretty similar so I'd at least be suspicious there 
too.

I'm not very familiar (ok, not at all) with the parser generation step, so 
there may be a few more questions along the way.

I should be able to take a quick look tonight sometime...
                
> 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-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.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]

Reply via email to