[ 
https://issues.apache.org/jira/browse/HIVE-26414?focusedWorklogId=797142&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-797142
 ]

ASF GitHub Bot logged work on HIVE-26414:
-----------------------------------------

                Author: ASF GitHub Bot
            Created on: 02/Aug/22 07:43
            Start Date: 02/Aug/22 07:43
    Worklog Time Spent: 10m 
      Work Description: deniskuzZ commented on code in PR #3457:
URL: https://github.com/apache/hive/pull/3457#discussion_r935221669


##########
ql/src/java/org/apache/hadoop/hive/ql/Driver.java:
##########
@@ -905,6 +905,11 @@ public QueryDisplay getQueryDisplay() {
     return driverContext.getQueryDisplay();
   }
 
+  @VisibleForTesting
+  DriverContext getDriverContext() {

Review Comment:
   no need to expose context in test. if you need queryPlan, you can simply 
call:
   ````
   driver.getPlan()
   ````





Issue Time Tracking
-------------------

    Worklog Id:     (was: 797142)
    Time Spent: 13h  (was: 12h 50m)

> Aborted/Cancelled CTAS operations must initiate cleanup of uncommitted data
> ---------------------------------------------------------------------------
>
>                 Key: HIVE-26414
>                 URL: https://issues.apache.org/jira/browse/HIVE-26414
>             Project: Hive
>          Issue Type: Improvement
>            Reporter: Sourabh Badhya
>            Assignee: Sourabh Badhya
>            Priority: Major
>              Labels: pull-request-available
>          Time Spent: 13h
>  Remaining Estimate: 0h
>
> When a CTAS query fails before creation of table and after writing the data, 
> the data is present in the directory and not cleaned up currently by the 
> cleaner or any other mechanism currently. This is because the cleaner 
> requires a table corresponding to what its cleaning. In order surpass such a 
> situation, we can directly pass the relevant information to the cleaner so 
> that such uncommitted data is deleted.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to