[
https://issues.apache.org/jira/browse/LUCENE-7219?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15332626#comment-15332626
]
ASF subversion and git services commented on LUCENE-7219:
---------------------------------------------------------
Commit f4362098f7290104205403b86e901c767c0c4d22 in lucene-solr's branch
refs/heads/branch_5_5 from [~steve_rowe]
[ https://git-wip-us.apache.org/repos/asf?p=lucene-solr.git;h=f436209 ]
LUCENE-7219: Add CHANGES entry
> (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
> Fix For: 5.x, 6.1, 6.0.1, master (7.0)
>
> 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]
