[
https://issues.apache.org/jira/browse/LUCENE-2262?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Muir updated LUCENE-2262:
--------------------------------
Attachment: LUCENE-2262.patch
initial patch:
* doesnt throw the exception for leading ? when matchVersion >= 3.1
* contrib's queryparser doesnt use Version, so i simply change
AllowLeadingWildcardProcessor
* the backwards tests will fail because LUCENE-2248: TestQueryParser uses
LUCENE_CURRENT when it should really be using some constant that resolves to
LUCENE_30: we can fix the test to use LUCENE_30 instead of LUCENE_CURRENT
> 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
>
>
> 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: java-dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: java-dev-h...@lucene.apache.org
