You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Ramkumar Aiyengar (JIRA)" <ji...@apache.org> on 2016/01/06 09:12:39 UTC

[jira] [Commented] (SOLR-8488) Add support for leading wildcards to ComplexPhraseQParserPlugin

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

Ramkumar Aiyengar commented on SOLR-8488:
-----------------------------------------

Functionally looks okay, but this should be opted in. Leading wildcards can be very costly and the user should consciously opt in to allow them..

> Add support for leading wildcards to ComplexPhraseQParserPlugin
> ---------------------------------------------------------------
>
>                 Key: SOLR-8488
>                 URL: https://issues.apache.org/jira/browse/SOLR-8488
>             Project: Solr
>          Issue Type: Improvement
>            Reporter: Varun Thacker
>            Priority: Minor
>             Fix For: 5.5, Trunk
>
>         Attachments: SOLR-8488.patch
>
>
> It would be useful to support leading wildcards in phrase searches as well. 
> Currently we support this query -
> {code}{!complexphrase inOrder=true}name:"Jo* Smith"{code}
> It would be useful to be support a query like -
> {code}{!complexphrase inOrder=true\}name:"*Jo* Smith"{code}



--
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