[WIP][SPARK-56284] Adding UDF worker specification protobuf definition#55165
Open
sven-weber-db wants to merge 1 commit intoapache:masterfrom
Open
[WIP][SPARK-56284] Adding UDF worker specification protobuf definition#55165sven-weber-db wants to merge 1 commit intoapache:masterfrom
sven-weber-db wants to merge 1 commit intoapache:masterfrom
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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 introduces the protobuf definitions for the UDF worker specification described in SPIP SPARK-55278 and this design document.
Overall, two new
.protofiles are introduced:common.proto- Shared types and messages between the worker specification & the new UDF protocol (to be introduced)worker_spec.proto- UDF worker specificationThe changes introduced in this PR depend on pull request 55089 and will be merged afterward.
Why are the changes needed?
This is the first step toward a language-agnostic UDF protocol for Spark that enables UDF workers written in any language to communicate with the Spark engine through a well-defined specification and API boundary. The abstractions introduced here establish the core contract that concrete implementations (e.g., process-based or gRPC-based workers) will build on.
The worker specification introduced in this PR captures all the information Spark needs to:
Does this PR introduce any user-facing change?
No. All new APIs are marked @experimental, and there are no behavioral changes to existing code.
How was this patch tested?
Was this patch authored or co-authored using generative AI tooling?
Yes, in an assistive manner and for reviews.