sryza commented on code in PR #52154:
URL: https://github.com/apache/spark/pull/52154#discussion_r2372645310
##########
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;
Review Comment:
Makes sense to me. My understanding was that, with the current backend
implementation, we only get one unresolved dependency at a time (because we
basically find out that it's missing when we hit a failure). However:
1. I might be wrong about that implementation
2. We could make a more sophisticated implementation in the future, and it
would be good if the protocol supports that
--
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]
