[jira] [Commented] (SOLR-7466) Allow optional leading wildcards in complexphrase

["Mikhail Khludnev (JIRA)" <ji...@apache.org>]

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

Mikhail Khludnev commented on SOLR-7466:
----------------------------------------

I tried to hook up {{ReversedWildcardFilterFactory}} SOLR-1321 in \{!complexphrase}. The problem is that 
{code}
 ComplexPhraseQueryParser --|> o.a.lucene.q.c.QueryParser
{code}
But a cool code, which leverages {{ReversedWildcardFilterFactory}} resides in {{o.a.solr...SolrQueryParserBase.getWildcardQuery(String, String)}}.
So far, I copy-pasted CPQP to make it descendant of Solr's parser. It works, but it's not cute. Is there a better idea? Is it really necessary to deal with RWFF?
 


> 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: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org