[SPARK-51722][SQL] Remove "stop" origin from ParseException #50518
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
viirya
reviewed
Apr 7, 2025
| case _ => | ||
| throw new ParseException( | ||
| command = None, | ||
| start = start, | ||
| stop = stop, |
There was a problem hiding this comment.
Oh, ParseException doesn't use stop actually.
There was a problem hiding this comment.
@viirya yes, for parser exception we just shall the start position with 3 ^s
viirya
reviewed
Apr 7, 2025
viirya
approved these changes
Apr 7, 2025
|
Thanks, merging to master |
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.
What changes were proposed in this pull request?
The "stop" origin from ParseException is not used. We should remove it to simplify code.
Why are the changes needed?
Code clean up
Does this PR introduce any user-facing change?
No
How was this patch tested?
Existing UT
Was this patch authored or co-authored using generative AI tooling?
No