[
https://issues.apache.org/jira/browse/LUCENE-2262?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Smiley updated LUCENE-2262:
---------------------------------
Fix Version/s: (was: 4.7)
4.8
> QueryParser should now allow leading '?' wildcards
> --------------------------------------------------
>
> Key: LUCENE-2262
> URL: https://issues.apache.org/jira/browse/LUCENE-2262
> Project: Lucene - Core
> Issue Type: Improvement
> Components: core/queryparser
> Affects Versions: 4.0-ALPHA
> Reporter: Robert Muir
> Assignee: Robert Muir
> Priority: Minor
> Fix For: 4.8
>
> Attachments: LUCENE-2262.patch, LUCENE-2262_backwards.patch
>
>
> QueryParser currently throws an exception if a wildcard term begins with the
> '?' operator.
> The current documentation describes why this is:
> {noformat}
> When set, * or ? are allowed as the first character of a PrefixQuery and
> WildcardQuery.
> Note that this can produce very slow queries on big indexes.
> {noformat}
> In the flexible indexing branch, wildcard queries with leading '?' operator
> are no longer slow on big indexes (they do not enumerate terms in linear
> fashion).
> Thus, it no longer makes sense to throw a ParseException for a leading '?'
> So, users should be able to perform a query of "?foo" and no longer get a
> ParseException from the QueryParser.
> For the flexible indexing branch, wildcard queries of 'foo?', '?foo',
> 'f?oo', etc are all the same from a performance perspective.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
