[
https://issues.apache.org/jira/browse/HIVE-21343?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16780203#comment-16780203
]
Jesus Camacho Rodriguez commented on HIVE-21343:
------------------------------------------------
Fix for this is part of the patch in HIVE-18920.
> CBO: CalcitePlanner debug logging is expensive and costly
> ---------------------------------------------------------
>
> Key: HIVE-21343
> URL: https://issues.apache.org/jira/browse/HIVE-21343
> Project: Hive
> Issue Type: Bug
> Components: CBO
> Affects Versions: 4.0.0
> Reporter: Gopal V
> Priority: Major
> Attachments: Reloptutil-toString.png,
> calcite-planner-after-fix.svg.zip
>
>
> {code}
> //Remove subquery
> LOG.debug("Plan before removing subquery:\n" +
> RelOptUtil.toString(calciteGenPlan));
> calciteGenPlan = hepPlan(calciteGenPlan, false,
> mdProvider.getMetadataProvider(), null,
> new HiveSubQueryRemoveRule(conf));
> LOG.debug("Plan just after removing subquery:\n" +
> RelOptUtil.toString(calciteGenPlan));
> calciteGenPlan = HiveRelDecorrelator.decorrelateQuery(calciteGenPlan);
> LOG.debug("Plan after decorrelation:\n" +
> RelOptUtil.toString(calciteGenPlan));
> {code}
> The LOG.debug() consumes more CPU than the actual planner steps.
> !Reloptutil-toString.png!
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
