[
https://issues.apache.org/jira/browse/HIVE-24596?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17293707#comment-17293707
]
Rajesh Balamohan commented on HIVE-24596:
-----------------------------------------
Lot of times, for debugging cbo & other aspects of query plans, users would
have to provide lot of details like query plans, table details, logs etc.
Certain times custom dev-jars are shipped to gather additional information,
and in some cases sample data is also requested from users.
{{explain ddl <query>}} helps in identifying the tables/views of the specific
query and generates the schema, partitions, stats, views for the specific
query. This way, dev has to just get this sql output and they can run it in
their local environment to reproduce the issue (i.e {{explain cbo <query>}} or
{{explain <query>}} should generate the same result without having real data).
This is targeted towards easier debugging. I haven't gone through the testcases
yet in the PR. I believe, it should cover examples and test cases, if not
present already.
> Explain ddl for debugging
> -------------------------
>
> Key: HIVE-24596
> URL: https://issues.apache.org/jira/browse/HIVE-24596
> Project: Hive
> Issue Type: Improvement
> Reporter: Rajesh Balamohan
> Assignee: Harshit Gupta
> Priority: Major
> Labels: pull-request-available
> Time Spent: 20m
> Remaining Estimate: 0h
>
> For debugging query issues, basic details like table schema, statistics,
> partition details, query plans are needed.
> It would be good to have "explain ddl" support, which can generate these
> details. This can help in recreating the schema and planner issues without
> sample data.
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
