feat(rust/sedona-expr): Use Covers filter for ST_Equals for more Geoparquet pruning #216
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Collaborator
Author
|
I noticed this when implementing #217. There will be a merge conflict that I will have to resolve. Doesn't matter to me which one is merged first. |
paleolimbot
changed the title
Kontinuation
approved these changes
Oct 13, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Previously, we've been using the Intersects filter for ST_Equals. This PR updates the SpatialFilter to use the Covers predicate for ST_Equals instead, which is more restrictive and should prune more data.
Continues to pass existing integration test that checks that we return the same non-empty result as the equivalent geopandas query.