lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Martin Blom (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (LUCENE-5664) New meaning of equal sign in StandardQueryParser
Date Sat, 10 May 2014 21:56:34 GMT

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

Martin Blom updated LUCENE-5664:
--------------------------------

    Attachment: LUCENE-5664.patch

> New meaning of equal sign in StandardQueryParser
> ------------------------------------------------
>
>                 Key: LUCENE-5664
>                 URL: https://issues.apache.org/jira/browse/LUCENE-5664
>             Project: Lucene - Core
>          Issue Type: Improvement
>          Components: modules/queryparser
>    Affects Versions: 4.5, 4.8
>            Reporter: Martin Blom
>         Attachments: LUCENE-5664.patch
>
>
> The StandardSyntaxParser.jj has (undocumented?) support for the <, <=, > and
=> operators that generate a TermRangeQueryNode. The equal operator, however, behaves just
like the colon and produces a regular Term node instead of a TermRangeQueryNode.
> I've been using the attached patch in a project where we had to be able to query the
exact value of a field and I'm hoping there is interest to apply it upstream.
> (Note that the colon operator works just as before, producing TermQuery or PhraseQuery
nodes.)



--
This message was sent by Atlassian JIRA
(v6.2#6252)

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


Mime
View raw message