[
https://issues.apache.org/jira/browse/LUCENE-7092?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15190975#comment-15190975
]
Robert Muir commented on LUCENE-7092:
-------------------------------------
I still think its ok to provide deprecated methods to do the conversion in the
meantime as mentioned. We did explain how to do these things in the javadocs
already.
But the previous booleans and nulls damaged the API beyond repair, especially
in the multi-dimensional case (boolean arrays). The previous "format" was also
ambiguous, e.g. that you can provide open+exclusive and other crazy
combinations.
With the current API for example its just:
{code}
IntPoint.newRangeQuery(Integer.MIN_VALUE, max); // open
IntPoint.newRangeQuery(min, max-1); // exclusive
FloatPoint.newRangeQuery(min, Math.nextDown(max)); // exclusive
FloatPoint.newRangeQuery(Float.NEGATIVE_INFINITY, max); // open
{code}
> Point range factory methods for excluded bounds
> -----------------------------------------------
>
> Key: LUCENE-7092
> URL: https://issues.apache.org/jira/browse/LUCENE-7092
> Project: Lucene - Core
> Issue Type: Improvement
> Reporter: Adrien Grand
> Priority: Minor
>
> I am playing with using the new points API with elasticsearch and one
> challenge is to generate range queries whose bounds are excluded, which is
> something that was very easy with the previous numerics implementation. It is
> easy to do externally with ints, but becomes tricky with floats or ip
> addresses. Maybe we should have factory methods that take 2 additional
> booleans to allow the bounds to be excluded?
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
