lucenenet-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Christopher Currens (Closed) (JIRA)" <j...@apache.org>
Subject [jira] [Closed] (LUCENENET-478) Parts of QueryParser are outdated or weren't previously ported correctly
Date Fri, 23 Mar 2012 01:34:23 GMT

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

Christopher Currens closed LUCENENET-478.
-----------------------------------------

    Resolution: Fixed

Decided to just scrap the entire class and port the java one from scratch.
                
> Parts of QueryParser are outdated or weren't previously ported correctly
> ------------------------------------------------------------------------
>
>                 Key: LUCENENET-478
>                 URL: https://issues.apache.org/jira/browse/LUCENENET-478
>             Project: Lucene.Net
>          Issue Type: Bug
>          Components: Lucene.Net Core
>    Affects Versions: Lucene.Net 2.9.4, Lucene.Net 2.9.4g
>            Reporter: Christopher Currens
>            Priority: Blocker
>              Labels: queryparser
>             Fix For: Lucene.Net 3.0.3
>
>
> Parts of the QueryParser class are _very_ old.  I'm not sure exactly how much of it is
old or hasn't even been ported, but I can say this probably has some effect on how the parser
differs from the java version.  I'm not sure about exact behavior differences, but this needs
to be ported from scratch again to make sure that it's on par with Java's queryparser.

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

        

Mime
View raw message