[WIP][SPARK-49690][SQL] UDT type not showing up in sql type representation in the schema #48174
+42
−5
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 is done as a rule in analyzer. I am not sure if that is the best way to handle the issue.
Why are the changes needed?
When showing the schema definition, the UDTType is presented as the ClassName of the UDT Type instead of the sql representation.
For eg: say message field is a UDT with sql representation as
StructField("intField", IntegerType, nullable = false),
StructField("stringField", StringType, nullable = false)))
But the schema contains it as
root
|-- message: test (nullable = true)
instead of
root
|-- message: struct (nullable = true)
| |-- intField: integer (nullable = false)
| |-- stringField: string (nullable = false)
Does this PR introduce any user-facing change?
Yes . The schema containing a UDT type will now be represented using its sql type.
How was this patch tested?
Added a bug test. More tests will be added..
Was this patch authored or co-authored using generative AI tooling?
No