[
https://issues.apache.org/jira/browse/LUCENE-7381?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15389769#comment-15389769
]
ASF subversion and git services commented on LUCENE-7381:
---------------------------------------------------------
Commit 1a94c25a04b1de80f8ae6e9c35f60ff97e9ec190 in lucene-solr's branch
refs/heads/branch_6x from [~nknize]
[ https://git-wip-us.apache.org/repos/asf?p=lucene-solr.git;h=1a94c25 ]
LUCENE-7381: Fix equals relation in RangeFieldQuery. Fix relation logic in
BaseRangeFieldQueryTestCase.
> 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,
> 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: [email protected]
For additional commands, e-mail: [email protected]
