[SPARK-49230][Connect][SQL] Do not return UnboundRowEncoder when not needed #49339
+30
−22
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
xupefei
changed the title
hvanhovell
reviewed
Dec 31, 2024
sql/api/src/main/scala/org/apache/spark/sql/catalyst/ScalaReflection.scala
Show resolved
Hide resolved
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?
This PR corrects the
isRowEncoderSupportedlogic ofencoderFormethod. Now when the flag is off,encoderFormethod will not return anUnboundRowEncoderbut instead throws an exception. To get back to the old behaviour, used one of the following two method instead:encoderFor(..., isRowEncoderSupported = true)encoderForWithRowEncoderSupport(...)To avoid breaking existing use cases, this PR changes some calls of
encoderFortoencoderForWithRowEncoderSupportwhen the input type involves genericT, sinceTcan be aRow.Why are the changes needed?
Code cleanup.
Does this PR introduce any user-facing change?
No. This method is used internally.
How was this patch tested?
Existing tests.
Was this patch authored or co-authored using generative AI tooling?
No.