[
https://issues.apache.org/jira/browse/LUCENE-7219?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15245698#comment-15245698
]
ASF subversion and git services commented on LUCENE-7219:
---------------------------------------------------------
Commit d268aef0ebd89901e8f91ae423ca606fbec7226e in lucene-solr's branch
refs/heads/branch_5x from [~cpoerschke]
[ https://git-wip-us.apache.org/repos/asf?p=lucene-solr.git;h=d268aef ]
LUCENE-7219: Make queryparser/xml NumericRange(Query|Filter) builders match the
underlying (query|filter)'s (lower|upper)Term optionality logic. (Kaneshanathan
Srivisagan, Christine Poerschke)
> (Point|LegacyNumeric)RangeQuery builders to match queries' (lower|upper)Term
> optionality logic
> ----------------------------------------------------------------------------------------------
>
> Key: LUCENE-7219
> URL: https://issues.apache.org/jira/browse/LUCENE-7219
> Project: Lucene - Core
> Issue Type: Bug
> Reporter: Christine Poerschke
> Assignee: Christine Poerschke
> Priority: Minor
> Attachments: LUCENE-7219.patch, LUCENE-7219.patch
>
>
> Currently the {{(Point|LegacyNumeric)RangeQuery}} queries themselves support
> {{(lower|upper)Term}} optionality e.g. the lowerTerm could be omitted but the
> {{(Point|LegacyNumeric)RangeQueryBuilder}} builders mandate
> {{(lower|upper)Term}} attributes. This mismatch seems unintended.
> Proposed patch for ...QueryBuilder logic to match ...Query logic to follow.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
