Fix categerization of partitioning handles for writer stage #23878
Conversation
This file contains 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
dekimir
approved these changes
Oct 23, 2024
We use different configuration of HashSplitAssigner based on partitining handle used by source stage. We want to determine if we are in write stage or not. The logic was wrong.
losipiuk
force-pushed
the
lukaszos/fix-categerization-of-partitioning-handles-for-writer-stage-1f55fe
branch
from
69a8011 to
0367798
Compare
wendigo
approved these changes
Oct 24, 2024
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.
We use different configuration of HashSplitAssigner based on partitining handle used by source stage. We want to determine if we are in write stage or not. The logic was wrong.