[SPARK-55202] Fix UNEXPECTED_USE_OF_PARAMETER_MARKER when using param… #53982
+20
−1
Conversation
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
…eter marke in spark-sql
srielau
changed the title
JIRA Issue Information=== Bug SPARK-55202 === This comment was automatically generated by GitHub Actions |
srielau
commented
Jan 26, 2026
sql/hive-thriftserver/src/test/scala/org/apache/spark/sql/hive/thriftserver/CliSuite.scala
Outdated
Show resolved
Hide resolved
gengliangwang
approved these changes
Jan 27, 2026
Member
|
Thanks, merging to master |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
…eter marke in spark-sql
What changes were proposed in this pull request?
Ensure pre-parser for parameter markers is called by spark-sql CLI
Why are the changes needed?
Without invoking the pre-parser, the presence of a parameter marker results in an internal error (UNEXPECTED_USE_OF_PARAMETER_MARKER).
By calling the pre-parser, this case is correctly detected and reported as UNBOUND_PARAMETER_MARKER, which is the expected behavior.
Does this PR introduce any user-facing change?
No
How was this patch tested?
New test added to CLI suite
Was this patch authored or co-authored using generative AI tooling?
Clause Sonnet