[jira] [Comment Edited] (LUCENE-7381) Add new RangeField

["Adrien Grand (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/LUCENE-7381?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15384486#comment-15384486 ] 

Adrien Grand edited comment on LUCENE-7381 at 7/19/16 4:48 PM:
---------------------------------------------------------------

This is an exciting feature! I looked at the patch and have some questions:
 - Should the field be called something like DoubleRange rather than RangeField so that we still have namespace to have similar fields for other data types? I think this would also be more consistent with the names of other fields like StringField or DoublePoint?
 - The reuse of {{fieldsData}} in {{setRangeValues}} worries me a bit, is it safe? Other fields do not seem to do that?
 - QueryType does not need to be public?
 - Why do you replace infinities with +/-MAX_VALUE?



was (Author: jpountz):
This is an eciting feature! I looked at the patch and have some questions:
 - Should the field be called something like DoubleRange rather than RangeField so that we still have namespace to have similar fields for other data types? I think this would also be more consistent with the names of other fields like StringField or DoublePoint?
 - The reuse of {{fieldsData}} in {{setRangeValues}} worries me a bit, is it safe? Other fields do not seem to do that?
 - QueryType does not need to be public?
 - Why do you replace infinities with +/-MAX_VALUE?


> Add new RangeField
> ------------------
>
>                 Key: LUCENE-7381
>                 URL: https://issues.apache.org/jira/browse/LUCENE-7381
>             Project: Lucene - Core
>          Issue Type: New Feature
>            Reporter: Nicholas Knize
>         Attachments: LUCENE-7381.patch, LUCENE-7381.patch, LUCENE-7381.patch
>
>
> I've been tinkering with a new Point-based {{RangeField}} for indexing numeric ranges that could be useful for a number of applications.
> For example, a single dimension represents a span along a single axis such as indexing calendar entries start and end time, 2d range could represent bounding boxes for geometric applications (e.g., supporting Point based geo shapes), 3d ranges bounding cubes for 3d geometric applications (collision detection, 3d geospatial), and 4d ranges for space time applications. I'm sure there's applicability for 5d+ ranges but a first incarnation should likely limit for performance.



--
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