-
Notifications
You must be signed in to change notification settings - Fork 29k
[SPARK-8309] [CORE] Support for more than 12M items in OpenHashMap #6763
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Closed
Closed
Changes from 1 commit
Commits
Show all changes
5 commits
Select commit
Hold shift + click to select a range
3920656
SPARK-8309: Support for more than 12M items in OpenHashMap
SlavikBaranov f9284fd
Resolved review comments
SlavikBaranov eaf1e68
Fixed failing test
SlavikBaranov 4d5b954
Resolved review comments
SlavikBaranov 8557445
Resolved review comments
SlavikBaranov File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Resolved review comments
- Loading branch information
commit 4d5b9543b60611a54a1c1023783d3078f4b0b214
There are no files selected for viewing
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
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I agree this is the theoretically largest number of elements that can be in the set. The failure will occur any time that twice the grow threshold exceeds
MAX_CAPACITY, which can happen when the collection is less full than this. So I am actually not sure what's clearer here. Up to you.I think we still have a little problem here, because when capacity reaches 2^30, twice that number becomes negative and
newCapacity <= OpenHashSet.MAX_CAPACITYis true, still, because of overflow. Check whether the existing capacity is<= OpenHashSet.MAX_CAPACITY / 2first?There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@srowen Integer overflow is not possible with current MAX_CAPACITY setting, since 2^31 is still positive number. Anyway, I've added check for positive capacity. IMO it's more clear way to guard against overflow.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
2^31 is positive, but it is not representable as a 32-bit signed int.
So that's an important check.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Oh, yes. Sorry :)