Details
-
Improvement
-
Status: Open
-
Major
-
Resolution: Unresolved
-
4.5, 4.8
-
None
-
None
-
New, Patch Available
Description
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.)