This repository has been archived by the owner on Sep 18, 2023. It is now read-only.
[NSE-1127] Use larger buffer for hash agg #1129
Merged
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
|
@jackylee-ch is this a real case? 2147483646 = 2GB |
Yes |
zhouyuan
approved these changes
Oct 12, 2022
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
What changes were proposed in this pull request?
Current hash aggegate use
StringHashMapto build hash table, which actually useStringBuilderto storage keys and its size is limited toInt.max-1. We meet the problem withCapacity error: array cannot contain more than 2147483646 bytes, have 2147483708while using aggeragate, it shows the origin buffer in hash map for hash aggerate is overflowed.Thus, we use
LargeStringHashMapto build hash table, which useLargeBinaryBuilderto storage keys and its size is limited toLong.max-1.How was this patch tested?
unit tests.