jiayuasu opened a new pull request, #3043:
URL: https://github.com/apache/sedona/pull/3043

   ## Did you read the Contributor Guide?
   
   - [x] Yes
   
   ## Is this PR related to a ticket?
   
   - [x] Yes — closes [#3042](https://github.com/apache/sedona/issues/3042); 
follow-up to the Box3D EPIC 
([#2973](https://github.com/apache/sedona/issues/2973)) and the Flink slices 
#3037 (foundation) and #3040 (accessors / ST_3DExtent).
   
   ## What changes were proposed in this PR?
   
   Final Flink Box3D slice. Brings the Flink predicate surface to parity with 
Spark's Box3D predicates (consolidated into `ST_Intersects` / `ST_Contains` 
plus the standalone `ST_3DDWithin`).
   
   - **`ST_Intersects` / `ST_Contains`**: Box3D `eval` overloads wrapping 
`Predicates.box3dIntersects` / `box3dContains`. Mirrors the Box2D overloads 
already on these classes.
   - **`ST_3DDWithin`**: new scalar function with two overloads — `(Geometry, 
Geometry, Double)` → `dWithin3D` (missing Z folds to 0), and `(Box3D, Box3D, 
Double)` → `dWithin3D`. NULL-guarded like the Box overloads. Registered in 
`Catalog`.
   
   ## How was this patch tested?
   
   - `PredicateTest.testIntersectsOnBox3D` / `testContainsOnBox3D` — 
XY-overlapping-but-Z-disjoint rows confirm the Z axis is enforced (not just an 
XY-footprint check).
   - `PredicateTest.test3DDWithin` — Geometry POINT Z within / just-outside the 
threshold, plus Box3D-on-Box3D faces-apart-in-Z within / just-outside.
   - Full `PredicateTest`: 21 pass.
   
   ## Did this PR include necessary documentation updates?
   
   - [x] No — Box3D documentation is tracked separately under the Box3D EPIC.
   
   ## Completion
   
   This completes Flink Box3D parity with the shipped Spark surface: type + 
serializer, constructors, accessors, `ST_AsText`, `ST_3DExtent`, and predicates.


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

Reply via email to