[
https://issues.apache.org/jira/browse/HIVE-12526?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15031250#comment-15031250
]
Jesus Camacho Rodriguez commented on HIVE-12526:
------------------------------------------------
[~hsubramaniyan], I have seen that you have added a single performance
measurement for Calcite planning.
I was wondering if we would like to have more precise measurements for Calcite,
as we have for the other Hive optimizations. For instance, (1) one per
optimization call, or (2) one per optimization block (prejoin reordering, join
reordering, postjoin reordering), or (3) -another option-. What do you think?
[~ashutoshc], what's your opinion?
> PerfLogger for hive compiler and optimizer
> ------------------------------------------
>
> Key: HIVE-12526
> URL: https://issues.apache.org/jira/browse/HIVE-12526
> Project: Hive
> Issue Type: Bug
> Reporter: Hari Sankar Sivarama Subramaniyan
> Assignee: Hari Sankar Sivarama Subramaniyan
> Attachments: HIVE-12526.1.patch
>
>
> This jira is intended to use the perflogger to track compilation times and
> optimization times (calcite, tez compiler, physical compiler) etc.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
