lucene-dev mailing list archives

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


Robert Muir commented on LUCENE-588:

This one came up recently on the mailing list: see

Again its technically easy to fix in 4.0, but we just need to decide if WildcardQuery/QueryParser
should just 
support escaped terms, instead of backwards compatibility stuff/Version/etc?

Even if we make it "fully backwards compatible" some things will need to change, 
for instance Solr's "reverse wildcard" support should instead reverse the actual Automaton
instead of the query string, this way it won't screw up the escapes... but this is
really cleaner anyway.

> 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
> 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