lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Yonik Seeley (JIRA)" <>
Subject [jira] [Commented] (SOLR-8488) Add support for leading wildcards to ComplexPhraseQParserPlugin
Date Thu, 07 Jan 2016 20:10:39 GMT


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:

> Add support for leading wildcards to ComplexPhraseQParserPlugin
> ---------------------------------------------------------------
>                 Key: SOLR-8488
>                 URL:
>             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

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message