[
https://issues.apache.org/jira/browse/LUCENE-2262?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12833481#action_12833481
]
Yonik Seeley commented on LUCENE-2262:
--------------------------------------
It doesn't seem like this type of bug is not one that people would rely on
(throwing an exception for ? but not for *), hence we should just fix and not
make it conditional on matchVersion?
> QueryParser should now allow leading '?' wildcards
> --------------------------------------------------
>
> Key: LUCENE-2262
> URL: https://issues.apache.org/jira/browse/LUCENE-2262
> Project: Lucene - Java
> Issue Type: Improvement
> Components: QueryParser
> Affects Versions: Flex Branch
> Reporter: Robert Muir
> Assignee: Robert Muir
> Priority: Minor
> Fix For: Flex Branch
>
> Attachments: LUCENE-2262.patch, LUCENE-2262_backwards.patch
>
>
> QueryParser currently throws an exception if a wildcard term begins with the
> ? operator.
> The docs say this:
> {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 flex branch, this is no longer true. foo?, ?foo, f?oo, these are all
> the same from a performance perspective.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
