lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Erick Erickson (Updated) (JIRA)" <>
Subject [jira] [Updated] (SOLR-2438) Case Insensitive Search for Wildcard Queries
Date Wed, 16 Nov 2011 01:02:51 GMT


Erick Erickson updated SOLR-2438:

    Attachment: SOLR-2438.patch

Here's a rough cut at what I *think* Yonik might have been talking about, comments?

I haven't done a thing about efficiency here, just seeing if the new method in the FilterFactories
(processQueryTerm) makes sense to y'all.

One thing I'm not clear on: Would it make more sense to just instantiate a new instance of
the filter and run each term through it rather than steal bits from the underlying Filters
(see ASCIIFoldingFilterFactory and LowercaseFilterFactory for example). I just hate duplicated
code but I'm not sure how efficient creating a new filter and running the token through would
be for each and every token.
> Case Insensitive Search for Wildcard Queries
> --------------------------------------------
>                 Key: SOLR-2438
>                 URL:
>             Project: Solr
>          Issue Type: Improvement
>            Reporter: Peter Sturge
>            Assignee: Erick Erickson
>         Attachments: 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:!default.jspa
For more information on JIRA, see:


To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message