Github user brkyvz commented on a diff in the pull request:
https://github.com/apache/spark/pull/16934#discussion_r101387562
--- Diff:
sql/core/src/main/scala/org/apache/spark/sql/execution/streaming/StreamExecution.scala
---
@@ -673,7 +673,7 @@ class StreamExecution(
if (lastExecution == null) {
"No physical plan. Waiting for data."
} else {
- val explain = ExplainCommand(lastExecution.logical, extended =
extended)
+ val explain = ExplainCommand(lastExecution.logical, extended =
extended, streaming = true)
--- End diff --
So this means that this code will always return an updated plan for the
last batch showing which data files were read instead of just referring to it
as a StreamingRelation. We wouldn't have the bug if we had just used
`logicalPlan` instead of `lastExecution.logicalPlan`, right? Then the problem
would be that the `logicalPlan` may contain errors though?
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: reviews-unsubscr...@spark.apache.org
For additional commands, e-mail: reviews-h...@spark.apache.org
