[
https://issues.apache.org/jira/browse/IMPALA-14916?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18078811#comment-18078811
]
Quanlong Huang commented on IMPALA-14916:
-----------------------------------------
+1 for using a new query option. We already have other options like
SHOW_COLUMN_MINMAX_STATS, SHOW_CREATE_TABLE_PARTITION_LIMIT controling the
output of metadata queries.
The new option can be orthogonal to EXPLAIN_LEVEL which can also control the
details level of the Calcite plan. BTW, do you have an example on how the
output looks like?
> Display Calcite plan in EXPLAIN output
> --------------------------------------
>
> Key: IMPALA-14916
> URL: https://issues.apache.org/jira/browse/IMPALA-14916
> Project: IMPALA
> Issue Type: Sub-task
> Reporter: Stamatis Zampetakis
> Priority: Major
>
> For performance analysis, debugging, and testing purposes it is useful to be
> able to display the Calcite plan in the EXPLAIN output.
> However, printing it always may be undesirable and noisy so we need a way to
> control when it is displayed or not. There are a few alternatives:
> * Dedicated command (EXPLAIN CALCITE)
> * New explain level (TExplainLevel.CALCITE)
> * New query option (e.g., ENABLE_EXPLAIN_CALCITE)
> If we treat the Calcite plan as additional info to be printed along with all
> the existing content of the EXPLAIN then the new option approach seems
> better. On the other hand, if we opt to display exclusively the Calcite plan
> with nothing more then a new explain level or command would make more sense.
> However, the explain levels so far are rather cumulative so to that respect a
> level that displays only the Calcite plan does not fit well in that model.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
