[
https://issues.apache.org/jira/browse/SOLR-8488?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15088019#comment-15088019
]
Yonik Seeley commented on SOLR-8488:
------------------------------------
For a common letter such as "a", each level may be 10 times more expensive than
the last... while it may make sense to *allow* for that to be limited, I don't
think it makes sense to hobble it by default. Its also not necessarily that
expensive compared to some other Solr operations like stats/facets on high
cardinality fields (and pivoted multiplies this).
Solr has normally allowed leading wildcards by default, and we should continue
that here.
For example, try:
http://localhost:8983/solr/techproducts/query?q=text:*olr
> 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: [email protected]
For additional commands, e-mail: [email protected]
