-
Notifications
You must be signed in to change notification settings - Fork 29k
[SPARK-43393][SQL] Address sequence expression overflow bug. #41072
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 all commits
Commits
Show all changes
15 commits
Select commit
Hold shift + click to select a range
efdf36e
Address overflow bug.
thepinetree 63d45fa
Add comment to point to issue.
thepinetree cd7dd84
Add edge-case test.
thepinetree b8d44fa
Address PR comments
thepinetree 4cde210
Merge branch 'master' into spark-sequence-overflow
thepinetree 03a5b50
Address comment
thepinetree 3297d8b
Scalastyle.
thepinetree 2fbe124
Merge branch 'master' into spark-sequence-overflow
thepinetree c3a6c77
Merge branch 'master' into spark-sequence-overflow
thepinetree a05fe02
Merge.
thepinetree 1100b28
Attempt addressing comments.
thepinetree b9592c8
Fixes.
thepinetree 85a793a
Fixes.
thepinetree 5cf0fc3
Remove dead line
thepinetree 83d56d4
Address comment.
thepinetree 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
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
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.
maybe just use an assert? Assertion error is also treated as internal errors.
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 personally like the current exception better since it's more descriptive of the actual problem -- trying to create too large an array (with the user's intended size) and what the limit is. If strong opinion, I can change to an assertion.