[
https://issues.apache.org/jira/browse/LUCENE-7381?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nicholas Knize updated LUCENE-7381:
-----------------------------------
Attachment: LUCENE-7381.patch
Updated patch:
* Fixes a bug found in the {{RangeFieldQuery}} relation logic where equal
ranges were not being returned with intersects, contains, and within queries
(adds explicit test for equals in {{testBasics}})
* Simplifies {{RangeFieldQuery}} relation logic
* Updates {{TestRangeFieldQueries}} to derive from a new
{{BaseRangeFieldQueryTestCase}} class allowing for testing new RangeField types
built on top of {{RangeField}} (e.g., date ranges, geo ranges)
* Fixes the test verification step to explicitly check intersect, contain, and
within while computing expected results. (The old patch was using the same
buggy logic in the RangeFieldQuery class.)
> 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: [email protected]
For additional commands, e-mail: [email protected]
