diff options
| author | Yanbo Liang <ybliang8@gmail.com> | 2015-02-25 15:37:13 -0800 |
|---|---|---|
| committer | Michael Armbrust <michael@databricks.com> | 2015-02-25 15:37:29 -0800 |
| commit | 5bd4b499a51b825419d9b0e61bba3050f53e8ab0 (patch) | |
| tree | d915213ee8087389cb530e342287cb456cc3ddfe /examples | |
| parent | 6fff9b8723085033b88103646ae28cafbecbf62f (diff) | |
| download | spark-5bd4b499a51b825419d9b0e61bba3050f53e8ab0.tar.gz spark-5bd4b499a51b825419d9b0e61bba3050f53e8ab0.tar.bz2 spark-5bd4b499a51b825419d9b0e61bba3050f53e8ab0.zip | |
[SPARK-5926] [SQL] make DataFrame.explain leverage queryExecution.logical
DataFrame.explain return wrong result when the query is DDL command.
For example, the following two queries should print out the same execution plan, but it not.
sql("create table tb as select * from src where key > 490").explain(true)
sql("explain extended create table tb as select * from src where key > 490")
This is because DataFrame.explain leverage logicalPlan which had been forced executed, we should use the unexecuted plan queryExecution.logical.
Author: Yanbo Liang <ybliang8@gmail.com>
Closes #4707 from yanboliang/spark-5926 and squashes the following commits:
fa6db63 [Yanbo Liang] logicalPlan is not lazy
0e40a1b [Yanbo Liang] make DataFrame.explain leverage queryExecution.logical
(cherry picked from commit 41e2e5acb749c25641f1f8dea5a2e1d8af319486)
Signed-off-by: Michael Armbrust <michael@databricks.com>
Diffstat (limited to 'examples')
0 files changed, 0 insertions, 0 deletions