Merge with V1.3.2 branch, and fix spatial join with nulls spanning vectors#663
Merged
Maxxen merged 8 commits intoduckdb:mainfrom Aug 17, 2025
Merged
Merge with V1.3.2 branch, and fix spatial join with nulls spanning vectors#663Maxxen merged 8 commits intoduckdb:mainfrom
Maxxen merged 8 commits intoduckdb:mainfrom
Conversation
fix prepared bounds not including next vertex of last segment
fix incorrect end node index access in large polygon-distance check
2 tasks
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Closes #662
Caused by the vector we fetch the join keys into not having its validity reset after each gathered chunk, causing the next vector to contain NULL's erroneously, which messes up the R-Tree as it gets fewer elements inserted than expected.