lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Robert Muir (Updated) (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (LUCENE-3981) queryparser precedence issues (regex versus wildcard)
Date Sat, 14 Apr 2012 14:59:17 GMT

     [ https://issues.apache.org/jira/browse/LUCENE-3981?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Robert Muir updated LUCENE-3981:
--------------------------------

    Attachment: LUCENE-3981.patch

While the above solution can work, it leaves things confusing and ambiguous in my opinion.

The simpler solution is to remove the ambiguity (so there is no concern about precedence/ordering
of fules) by adding "/" as a syntax char: patch fixes this for both core and flexible QPs
and adds a lot of tests that both escaping and quoting work sanely.

                
> queryparser precedence issues (regex versus wildcard)
> -----------------------------------------------------
>
>                 Key: LUCENE-3981
>                 URL: https://issues.apache.org/jira/browse/LUCENE-3981
>             Project: Lucene - Java
>          Issue Type: Bug
>    Affects Versions: 4.0
>            Reporter: Robert Muir
>         Attachments: LUCENE-3981.patch
>
>
> As mentioned by lance on LUCENE-2604,
> REGEXPTERM needs to be moved in front of WILDTERM and PREFIXTERM,
> because they greedily match operators like ".*" even inside / / blocks.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org


Mime
View raw message