[SPARK-53802][SDP] Support string values for user-specified schema in SDP tables #52517
+166
−55
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
sryza
force-pushed
the
dataset-schema-string
branch
from
50b839e to
cb8ba44
Compare
| assert(graph.tables.size == 1) | ||
|
|
||
| val table = graph.table(graphIdentifier("table_with_string_schema")) | ||
| assert(table.specifiedSchema.isDefined) |
There was a problem hiding this comment.
nit: shall we simply compare table.specifiedSchema with an expected schema (for example, StructType.fromDDL(id LONG, name STRING))
| optional spark.connect.DataType schema = 7; | ||
| oneof schema { | ||
| spark.connect.DataType schema_data_type = 7; | ||
| string schema_string = 10; |
There was a problem hiding this comment.
since Spark 4.1 is not offically released. I wonder if we can change the sequence numbers here.
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?
When defining a streaming table or materialized view, enable passing a string to its schema, in addition to a StructType. This mimics the flexibility of the
DataFrameReaderschema arg.E.g.
Why are the changes needed?
For flexibility and consistency with similar args.
Does this PR introduce any user-facing change?
Makes changes to unreleased protos.
How was this patch tested?
Was this patch authored or co-authored using generative AI tooling?