[
https://issues.apache.org/jira/browse/SOLR-8488?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15088100#comment-15088100
]
Ramkumar Aiyengar commented on SOLR-8488:
-----------------------------------------
I get that consistency with the normal phrase queries will be good, do keep in
mind that cpq makes it even easier to shoot yourself in your foot, "*a *b *c"
for example. Also enabling it by default would also be a compatibility break
for 5x at least.
For trunk, fine, I am not too opinionated about the default, as long as there's
an option to block it. And if we are looking to be consistent, should other
parsers also honor this option?
> 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, 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-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
