You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Mikhail Khludnev (JIRA)" <ji...@apache.org> on 2016/12/15 17:54:58 UTC
[jira] [Updated] (SOLR-7466) Allow optional leading wildcards in
complexphrase
[ https://issues.apache.org/jira/browse/SOLR-7466?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Mikhail Khludnev updated SOLR-7466:
-----------------------------------
Attachment: SOLR-7466.patch
What would you think about [^SOLR-7466.patch]? We can add SolrQP as mixing to Lucene's ComplexPhraseQP and delegate wildcards to the former!
> 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
> 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
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org