You are viewing a plain text version of this content. The canonical link for it is here.
Posted to reviews@spark.apache.org by GitBox <gi...@apache.org> on 2019/07/29 07:48:09 UTC
[GitHub] [spark] cloud-fan commented on issue #25280: [SPARK-28548][SQL]
explain() shows wrong result for persisted DataFrames after some operations
cloud-fan commented on issue #25280: [SPARK-28548][SQL] explain() shows wrong result for persisted DataFrames after some operations
URL: https://github.com/apache/spark/pull/25280#issuecomment-515884006
It's by design that a dataframe can't change its physical plan once the physical plan is materialized. That said, `df.persist` has no effect if `df.explain` is called before.
I think the current behavior is corrected and v2.4.3 is wrong. I think this problem is fixed by https://github.com/apache/spark/pull/24654
If you do wanna run the plan with cached data, maybe we can do `val df2 = df.toDF()` and execute `df2` instead.
----------------------------------------------------------------
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.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
With regards,
Apache Git Services
---------------------------------------------------------------------
To unsubscribe, e-mail: reviews-unsubscribe@spark.apache.org
For additional commands, e-mail: reviews-help@spark.apache.org