lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Robert Muir (JIRA)" <>
Subject [jira] Updated: (LUCENE-588) Escaped wildcard character in wildcard term not handled correctly
Date Thu, 04 Nov 2010 16:14:13 GMT


Robert Muir updated LUCENE-588:

    Attachment: LUCENE-588.patch

here's a patch: i also fixed SolrQueryParser not to reverse the query string, but instead
the actual automaton.
This way, it has no problems with what is escaped and what isn't.

additionally its ReverseWildcard tests needed some revamping... they were using Query.toString
to check
if a term was reversed or not... but with this approach its transparent and we don't work
on Strings.

But i couldn't figure out the contrib/queryparser... i left a test with @Ignore for now that

> Escaped wildcard character in wildcard term not handled correctly
> -----------------------------------------------------------------
>                 Key: LUCENE-588
>                 URL:
>             Project: Lucene - Java
>          Issue Type: Bug
>          Components: QueryParser
>    Affects Versions: 2.0.0
>         Environment: Windows XP SP2
>            Reporter: Sunil Kamath
>            Assignee: Michael Busch
>            Priority: Minor
>             Fix For: 4.0
>         Attachments: LUCENE-588.patch, LUCENE-588.patch, LUCENE-588.patch
> If an escaped wildcard character is specified in a wildcard query, it is treated as a
wildcard instead of a literal.
> e.g., t\??t is converted by the QueryParser to t??t - the escape character is discarded.

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:
For additional commands, e-mail:

View raw message