pranavbhole opened a new pull request, #16029:
URL: https://github.com/apache/druid/pull/16029

   ### Description
   
   1. This PR creates an interface for ImmutableRTree and moved the existing 
implementation to Legacy class for backward compatibility (stores coordinate as 
floats).  
   2. In all spatial bound filters, we accept float as input which might not be 
accurate in the case of high precision implementation of ImmutableRTree. This 
PR changed the bound filters to accepts the query bounds as double instead of 
float and it is backward compatible change as it compares double to existing 
float values in RTree.  Previously it was comparing input float to RTree floats 
which can cause precision loss, now it is little better as it compares double 
to float which is still not 100% accurate.
   3.  There are no changes in the way that we query spatial dimension today 
except input bound parsing. There is little improvement in string filter 
predicate which now parse double strings instead of float and compares double 
to double which is 100% accurate but string predicate is only called when we 
dont have spatial index. 
   4. With allowing the interface to extend ImmutableRTree, we allow to create 
high precision (HP) implementation and defines new search strategies to perform 
HP search `Iterable<ImmutableBitmap> search(ImmutableDoubleNode node, Bound 
bound);`
   5. With possible HP implementations, There was bug in Radius bound filter, 
it was calculating Euclidean distance in comparing. As EARTH 🌍  is round 
Euclidean distances are not accurate, thus using 
https://en.wikipedia.org/wiki/Haversine_formula to check if given geo point 
falls inside circle or not. Added a test that generates set of points inside 
and outside in RadiusBoundTest.
   
   PR is fully backward compatible, Just adding a note that we plan to 
deprecate the Legacy implementation of RTree somewhere down the line. Let me 
know if you have any questions.
   
   This PR has:
   
   - [ ] been self-reviewed.
      - [ ] using the [concurrency 
checklist](https://github.com/apache/druid/blob/master/dev/code-review/concurrency.md)
 (Remove this item if the PR doesn't have any relation to concurrency.)
   - [ ] added documentation for new or modified features or behaviors.
   - [ ] a release note entry in the PR description.
   - [ ] added Javadocs for most classes and all non-trivial methods. Linked 
related entities via Javadoc links.
   - [ ] added or updated version, license, or notice information in 
[licenses.yaml](https://github.com/apache/druid/blob/master/dev/license.md)
   - [ ] added comments explaining the "why" and the intent of the code 
wherever would not be obvious for an unfamiliar reader.
   - [ ] added unit tests or modified existing tests to cover new code paths, 
ensuring the threshold for [code 
coverage](https://github.com/apache/druid/blob/master/dev/code-review/code-coverage.md)
 is met.
   - [ ] added integration tests.
   - [ ] been tested in a test Druid cluster.
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to