[
https://issues.apache.org/jira/browse/SOLR-7466?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15663014#comment-15663014
]
Mikhail Khludnev commented on SOLR-7466:
----------------------------------------
Or how to move ReversedWildcardFilterFactory into Lucene and let Lucene's query
parser to detect it in analysis chain like it's done in
o.a.solr.p.SolrQueryParserBase.getReversedWildcardFilterFactory(FieldType) ?
Isn't there anything in Lucene which gets on par with Solr's one?
> Allow optional leading wildcards in complexphrase
> -------------------------------------------------
>
> Key: SOLR-7466
> URL: https://issues.apache.org/jira/browse/SOLR-7466
> Project: Solr
> Issue Type: Improvement
> Components: query parsers
> Affects Versions: 4.8
> Reporter: Andy hardin
> Labels: complexPhrase, query-parser, wildcards
>
> 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
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
