[jira] [Commented] (LUCENE-5664) New meaning of equal sign in StandardQueryParser

["Martin Blom (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/LUCENE-5664?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16644561#comment-16644561 ] 

Martin Blom commented on LUCENE-5664:
-------------------------------------

OK, I realize this late reply is just ridiculous, but ...

Yes, it's exactly the same comparison as the other operators, i.e. _name="some value"_ behaves just like _name>="some value" AND name<="some value"_.

 

> 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
>            Priority: Major
>         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
(v7.6.3#76005)

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