You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Steve Rowe (JIRA)" <ji...@apache.org> on 2016/05/19 18:21:12 UTC
[jira] [Updated] (LUCENE-7219) (Point|LegacyNumeric)RangeQuery
builders to match queries' (lower|upper)Term optionality logic
[ https://issues.apache.org/jira/browse/LUCENE-7219?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Steve Rowe updated LUCENE-7219:
-------------------------------
Fix Version/s: (was: 6.x)
(was: 6.0)
master (7.0)
6.1
> (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, 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: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org