-
Notifications
You must be signed in to change notification settings - Fork 28.9k
[SPARK-53796][SDP] Add extension
field to a few pipeline protos to support forward compatibility
#52514
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: master
Are you sure you want to change the base?
[SPARK-53796][SDP] Add extension
field to a few pipeline protos to support forward compatibility
#52514
Conversation
extension
field to pipeline protos to support forward compatibility
extension
field to pipeline protos to support forward compatibilityextension
field to pipeline protos to support forward compatibility
sql/connect/common/src/main/protobuf/spark/connect/pipelines.proto
Outdated
Show resolved
Hide resolved
sql/connect/common/src/main/protobuf/spark/connect/pipelines.proto
Outdated
Show resolved
Hide resolved
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM!
Hi @vicennial @hvanhovell, wondering whether yall wanna take a look at this PR. This PR is adding extension field to the DefineDataset and DefineFlow proto to support databricks only field |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
extension
field to pipeline protos to support forward compatibilityextension
field to a few pipeline protos to support forward compatibility
extension
field to a few pipeline protos to support forward compatibilityextension
field to a few pipeline protos to support forward compatibility
What changes were proposed in this pull request?
Adding
google.protobuf.Any extension = 999;
field toPipelineCommand
andSourceCodeLocation
Protos to support forward-compatibility by carrying additional pipeline command types, source code location fields that are not yet defined in this version of the proto.During the planning stage, the Spark Server will resolve and dispatch command / message to the correct handler.
Why are the changes needed?
To support forward-compatibility by carrying additional pipeline command types / dataset or flow's fields that are not yet defined in this version of the proto. Useful for platforms that want to extend pipeline commands with platform-specific capabilities.
Does this PR introduce any user-facing change?
No
How was this patch tested?
Test will be added for feature works using this new field
Was this patch authored or co-authored using generative AI tooling?
No