[
https://issues.apache.org/jira/browse/SPARK-27395?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Xiao Li updated SPARK-27395:
----------------------------
Description:
Currently, when the query is complex or the output schema is long, the outputs
of our EXPAIN command are not readable. Our documentation does not explain how
to read the plans [e.g., the meaning of each field]. It is confusing to end
users. The current format limits us to add more more useful details to each
operator, since it is already very long. We need to reformat the query plans
for better readability.
In this release, we need to improve the usability and documentation of EXPLAIN.
was:Currently, when the query is complex or the output schema is long, the
outputs of our EXPAIN command are not readable. Our documentation does not
document how to read the plans. It is confusing to end users. In this release,
we need to improve the usability and documentation of EXPLAIN. For example,
reformatting the outputs of EXPLAIN and we can add more useful details of each
operator.
> Improve EXPLAIN command
> -----------------------
>
> Key: SPARK-27395
> URL: https://issues.apache.org/jira/browse/SPARK-27395
> Project: Spark
> Issue Type: Umbrella
> Components: SQL
> Affects Versions: 3.0.0
> Reporter: Xiao Li
> Priority: Major
>
> Currently, when the query is complex or the output schema is long, the
> outputs of our EXPAIN command are not readable. Our documentation does not
> explain how to read the plans [e.g., the meaning of each field]. It is
> confusing to end users. The current format limits us to add more more useful
> details to each operator, since it is already very long. We need to reformat
> the query plans for better readability.
> In this release, we need to improve the usability and documentation of
> EXPLAIN.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@spark.apache.org
For additional commands, e-mail: issues-h...@spark.apache.org
