Skip to content

Conversation

sryza
Copy link
Contributor

@sryza sryza commented Oct 6, 2025

What changes were proposed in this pull request?

  • In `DefineDataset', pulls out all the properties that are table-specific into their own sub-message.
  • In DefineFlow, pulls out the relation property into its own sub-message.

Why are the changes needed?

The DefineDataset and DefineFlow Spark Connect protos are moshpits of properties that could be refactored into a more coherent structure:

  • In DefineDataset, there are a set of properties that are only relevant to tables (not views). They can be
  • In DefineFlow, the relation property refers to flows that write the results of a relation to a target table. In the future, we may want to introduce additional flows types that mutate the target table in different ways.

Does this PR introduce any user-facing change?

No, these protos haven't been shipped yet.

How was this patch tested?

Updated existing tests.

Was this patch authored or co-authored using generative AI tooling?

Copy link
Contributor

@SCHJonathan SCHJonathan left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

mostly LGTM with one minor comment

optional SourceCodeLocation source_code_location = 6;

oneof details {
WriteRelationFlowDetails relation_flow_details = 7;
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

open to discussion, wdyt we define a ImplicitFlowDetails that only has relation, and StandaloneFlowDetails that has flow_name, relation and potential optional bool once in the future.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants