[
https://issues.apache.org/jira/browse/HIVE-26414?focusedWorklogId=796830&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-796830
]
ASF GitHub Bot logged work on HIVE-26414:
-----------------------------------------
Author: ASF GitHub Bot
Created on: 01/Aug/22 09:33
Start Date: 01/Aug/22 09:33
Worklog Time Spent: 10m
Work Description: SourabhBadhya commented on code in PR #3457:
URL: https://github.com/apache/hive/pull/3457#discussion_r934330597
##########
standalone-metastore/metastore-common/src/main/java/org/apache/hadoop/hive/metastore/IMetaStoreClient.java:
##########
@@ -3478,6 +3478,17 @@ CompactionResponse compact2(String dbname, String
tableName, String partitionNam
*/
ShowCompactResponse showCompactions() throws TException;
+ /**
+ * Submit a request for performing cleanup of output directory. This is
particularly
+ * useful for CTAS when the query fails after write and before creation of
table.
+ * @return Status of whether the request was successfully submitted. True
indicates
+ * the request was successfully submitted and false indicates failure of
request submitted.
+ * @throws TException
+ */
+ boolean submitForCleanup(String dbname, String tableName, CompactionType
type,
Review Comment:
As discussed offline, this was already done. The request is created inside
this function which actually makes the request to the HMS.
Issue Time Tracking
-------------------
Worklog Id: (was: 796830)
Time Spent: 8h 40m (was: 8.5h)
> 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: 8h 40m
> 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)
