fix: partition evaluator thread safety#115
Merged
Fokko merged 1 commit intoapache:mainfrom Nov 2, 2023
skellys:fix/partition_evaluator_thread_safety
Merged
fix: partition evaluator thread safety#115Fokko merged 1 commit intoapache:mainfrom skellys:fix/partition_evaluator_thread_safety
Fokko merged 1 commit intoapache:mainfrom
skellys:fix/partition_evaluator_thread_safety
Conversation
Contributor
|
Looks great to me Sean! |
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
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.
I found a thread safety bug where some unwanted partitions would make it past the partition filter. I found and tested this fix on a simple Iceberg table with one schema spec, 5 manifest files (so 5 threads used in the thread pool), and thousands of partitions.
I've also solved this with a thread local storage approach to create fewer
_ExpressionEvaluatorinstances under the hood, but I didn't think that'd be worth the additional complexity, especially with per-thread cleanup.TODO