[
https://issues.apache.org/jira/browse/HIVE-25046?focusedWorklogId=599787&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-599787
]
ASF GitHub Bot logged work on HIVE-25046:
-----------------------------------------
Author: ASF GitHub Bot
Created on: 20/May/21 13:00
Start Date: 20/May/21 13:00
Worklog Time Spent: 10m
Work Description: zabetak commented on pull request #2205:
URL: https://github.com/apache/hive/pull/2205#issuecomment-845096727
Tests are green can we get this in @jcamachor ?
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
[email protected]
Issue Time Tracking
-------------------
Worklog Id: (was: 599787)
Time Spent: 50m (was: 40m)
> Log CBO plans right after major transformations
> -----------------------------------------------
>
> Key: HIVE-25046
> URL: https://issues.apache.org/jira/browse/HIVE-25046
> Project: Hive
> Issue Type: Improvement
> Components: CBO
> Reporter: Stamatis Zampetakis
> Assignee: Stamatis Zampetakis
> Priority: Major
> Labels: pull-request-available
> Time Spent: 50m
> Remaining Estimate: 0h
>
> Currently the results of various CBO transformations are logged (in DEBUG
> mode) at the end of the optimization
> [phase|https://github.com/apache/hive/blob/9f5bd72e908244b2fe915e8dc39f55afa94bbffa/ql/src/java/org/apache/hadoop/hive/ql/parse/CalcitePlanner.java#L2106]
> and only if we are not in test mode. This has some disadvantages:
> * If there is a failure (exception) in some intermediate step we will miss
> all the intermediate plans, possibly losing track of what plan led to the
> problem.
> * Intermediate logs are very useful for identifying plan problems while
> working on a patch; unfortunately the logs are explicitly disabled in test
> mode which means that in order to appear the respective code needs to change
> every time we need to see those logs.
> * Logging at the end necessitates keeping additional local variables that
> make code harder to read.
> The goal of this issue is to place DEBUG logging right after major
> transformations and independently if we are running in test mode or not to
> alleviate the shortcomings mentioned above.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
