[
https://issues.apache.org/jira/browse/HIVE-25535?focusedWorklogId=653377&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-653377
]
ASF GitHub Bot logged work on HIVE-25535:
-----------------------------------------
Author: ASF GitHub Bot
Created on: 21/Sep/21 05:19
Start Date: 21/Sep/21 05:19
Worklog Time Spent: 10m
Work Description: ashish-kumar-sharma commented on a change in pull
request #2651:
URL: https://github.com/apache/hive/pull/2651#discussion_r712701687
##########
File path: ql/src/java/org/apache/hadoop/hive/ql/txn/compactor/Cleaner.java
##########
@@ -179,6 +180,13 @@ private void clean(CompactionInfo ci, long minOpenTxnGLB,
boolean metricsEnabled
txnHandler.markCleaned(ci);
return;
}
+ if (MetaStoreUtils.isNoCleanUpSet(t.getParameters())) {
+ // The table was marked no clean up true.
+ LOG.info("Skipping " + ci.getFullTableName() + " clean up, as
NO_CLEANUP set to true");
+ txnHandler.markCleaned(ci);
Review comment:
@deniskuzZ I agree with you there will be some obsolete files could stay
forever only if user is replying on auto compaction. This config is for user
who manually trigger compaction in there data pipelines. i.e
ALTER TABLE table_name COMPACT 'major' WITH OVERWRITE TBLPROPERTIES
("no_cleanup"="true");
{some ETL operation}
ALTER TABLE table_name COMPACT 'major' WITH OVERWRITE TBLPROPERTIES
("no_cleanup"="false");
Any hive query/ETL pipeline always refer to handful of table. So disabling
Cleaner completely will increase the blast radius and over head for cleaner. if
a user forget to revert no_cleanup back to false then it will have performance
impact which we should document in hive wiki.
--
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.
To unsubscribe, e-mail: gitbox-unsubscr...@hive.apache.org
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
Issue Time Tracking
-------------------
Worklog Id: (was: 653377)
Time Spent: 1h 50m (was: 1h 40m)
> Control cleaning obsolete directories/files of a table via property
> -------------------------------------------------------------------
>
> Key: HIVE-25535
> URL: https://issues.apache.org/jira/browse/HIVE-25535
> Project: Hive
> Issue Type: Improvement
> Reporter: Ashish Sharma
> Assignee: Ashish Sharma
> Priority: Major
> Labels: pull-request-available
> Time Spent: 1h 50m
> Remaining Estimate: 0h
>
> *Use Case* -
> When external tool like [SPARK_ACID |https://github.com/qubole/spark-acid]try
> to access hive metastore directly instead of accessing LLAP or hs2 which
> lacks the ability of take acquires locks on the metastore artefacts. Due to
> which if any spark acid jobs starts and at the same time compaction happens
> in hive with leads to exceptions like *FileNotFound* for delta directory
> because at time of spark acid compilation phase delta files are present but
> when execution start delta files are deleted by compactor.
> Inorder to tackle problem like this I am proposing to add a config
> "NO_CLEANUP" is table properties and partition properties which provide
> higher control on table and partition compaction process.
> We already have
> "[HIVE_COMPACTOR_DELAYED_CLEANUP_ENABLED|https://github.com/apache/hive/blob/71583e322fe14a0cfcde639629b509b252b0ed2c/common/src/java/org/apache/hadoop/hive/conf/HiveConf.java#L3243]";
> which allow us to delay the deletion of "obsolete directories/files" but it
> is applicable to all the table in metastore where this config will provide
> table and partition level control.
> *Solution* -
> Add "NO_CLEANUP" in the table properties enable/disable the table-level and
> partition cleanup and prevent the cleaner process from automatically cleaning
> obsolete directories/files.
> Example -
> ALTER TABLE <tablename> SET TBLPROPERTIES('NO_CLEANUP'=FALSE/TRUE);
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
