SCHJonathan commented on code in PR #52154:
URL: https://github.com/apache/spark/pull/52154#discussion_r2363759691
##########
sql/connect/common/src/main/protobuf/spark/connect/pipelines.proto:
##########
@@ -90,6 +92,24 @@ message PipelineCommand {
optional string format = 8;
}
+ // Metadata about why a query function failed to be executed successfully.
+ message QueryFunctionFailure {
+ // Identifier for a dataset within the graph that the query function
needed to know the schema
+ // of but which had not yet been analyzed itself.
+ optional string missing_dependency = 1;
+ }
+
+ // The result of executing a user-defined query function.
+ message QueryFunctionResult {
+ oneof flow_function_evaluation_result {
+ // If the query function executed successfully, the unresolved logical
plan produced by it.
+ spark.connect.Relation plan = 1;
Review Comment:
This is what we do today. SC client run the MV function and lazily analyze
into a unresolved logical plan. The SC client will pass the unresolved logical
plan to the server (LDP engine) through the DefineFlow RPC so that the server
can resolve the flow based on resolved dependencies from the DataflowGraph
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
