[
https://issues.apache.org/jira/browse/HIVE-26414?focusedWorklogId=793093&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-793093
]
ASF GitHub Bot logged work on HIVE-26414:
-----------------------------------------
Author: ASF GitHub Bot
Created on: 20/Jul/22 08:35
Start Date: 20/Jul/22 08:35
Worklog Time Spent: 10m
Work Description: pvary commented on code in PR #3457:
URL: https://github.com/apache/hive/pull/3457#discussion_r925331780
##########
ql/src/java/org/apache/hadoop/hive/ql/lockmgr/DbTxnManager.java:
##########
@@ -485,6 +480,26 @@ private void clearLocksAndHB() {
stopHeartbeat();
}
+ private void cleanupDirForCTAS() {
Review Comment:
Do I understand correctly, that we do not create a table for CTAS, we just
create a `destinationTable` object which behaves as a table, but it is not
created in the HMS?
So basically we do not really have to drop the table, we just have to drop
the directory?
Issue Time Tracking
-------------------
Worklog Id: (was: 793093)
Time Spent: 20m (was: 10m)
> 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: 20m
> 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)
