lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Erick Erickson (JIRA)" <>
Subject [jira] [Commented] (SOLR-7466) Allow optional leading wildcards in complexphrase
Date Fri, 30 Dec 2016 03:27:58 GMT


Erick Erickson commented on SOLR-7466:


I haven't looked at the code, so take this with a large grain of salt. 

My only concern is if having this on by default would cause a full terms scan. If having this
always on by default means a user can use a leading wildcard without specifying ReverseWildcardFilterFactory
in the analysis chain then it seems trappy.

That said, I'll defer to your familiarity with the, you know, actual code.

> Allow optional leading wildcards in complexphrase
> -------------------------------------------------
>                 Key: SOLR-7466
>                 URL:
>             Project: Solr
>          Issue Type: Improvement
>          Components: query parsers
>    Affects Versions: 4.8
>            Reporter: Andy hardin
>            Assignee: Mikhail Khludnev
>              Labels: complexPhrase, query-parser, wildcards
>         Attachments: SOLR-7466.patch
> Currently ComplexPhraseQParser (SOLR-1604) allows trailing wildcards on terms in a phrase,
but does not allow leading wildcards.  I would like the option to be able to search for terms
with both trailing and leading wildcards.  
> For example with:
> {!complexphrase allowLeadingWildcard=true} "j* *th"
> would match "John Smith", "Jim Smith", but not "John Schmitt"

This message was sent by Atlassian JIRA

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

View raw message