-
Couldn't load subscription status.
- Fork 28.9k
[SPARK-52762][SDP] Add PipelineAnalysisContext message to support pipeline analysis during Spark Connect query execution #52685
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
Conversation
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
sql/connect/common/src/main/protobuf/spark/connect/pipelines.proto
Outdated
Show resolved
Hide resolved
| optional string dataflow_graph_id = 1; | ||
|
|
||
| // Defines the path assigned at runtime when the pipeline initializes | ||
| optional string definition_path = 2; |
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.
We determined that we need a corresponding field on SourceCodeLocation, right? Also, perhaps we should give this consistent naming with the file_name field there? Perhaps outer_file_name?
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.
Discussed to be definition_path. added to SourceCodeLocation.
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!
What changes were proposed in this pull request?
This PR introduces a new protobuf message, PipelineAnalysisContext, in ect/common/src/main/protobuf/spark/connect/pipelines.proto.
Why are the changes needed?
Special handling is needed for spark.sql in certain contexts. This proto provides a foundation for passing such context in future.
Does this PR introduce any user-facing change?
No, it only adds an internal protobuf message.
How was this patch tested?
Verified through protobuf compilation and existing test coverage.
Was this patch authored or co-authored using generative AI tooling?
No.