You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hive.apache.org by "ASF GitHub Bot (Jira)" <ji...@apache.org> on 2020/10/16 10:32:00 UTC
[jira] [Work logged] (HIVE-24275) Configurations to delay the
deletion of obsolete files by the Cleaner
[ https://issues.apache.org/jira/browse/HIVE-24275?focusedWorklogId=501509&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-501509 ]
ASF GitHub Bot logged work on HIVE-24275:
-----------------------------------------
Author: ASF GitHub Bot
Created on: 16/Oct/20 10:31
Start Date: 16/Oct/20 10:31
Worklog Time Spent: 10m
Work Description: vpnvishv opened a new pull request #1583:
URL: https://github.com/apache/hive/pull/1583
<!--
Thanks for sending a pull request! Here are some tips for you:
1. If this is your first time, please read our contributor guidelines: https://cwiki.apache.org/confluence/display/Hive/HowToContribute
2. Ensure that you have created an issue on the Hive project JIRA: https://issues.apache.org/jira/projects/HIVE/summary
3. Ensure you have added or run the appropriate tests for your PR:
4. If the PR is unfinished, add '[WIP]' in your PR title, e.g., '[WIP]HIVE-XXXXX: Your PR title ...'.
5. Be sure to keep the PR description updated to reflect all changes.
6. Please write your PR title to summarize what this PR proposes.
7. If possible, provide a concise example to reproduce the issue for a faster review.
-->
### What changes were proposed in this pull request?
Added support to delay cleanup of obsolete files/dirs with user configured value.
I have just ported this change from Qubole's hive-3 branch to master with some changes, it still requires thorough review wrt to Master branch. In this change we have reused CQ_META_INFO field from COMPACTION_QUEUE to store compaction end time. As we didn't wanted to change schema in branch-3. This can be changed in master by adding a new field in compaction_queue.
<!--
Please clarify what changes you are proposing. The purpose of this section is to outline the changes and how this PR fixes the issue.
If possible, please consider writing useful notes for better and faster reviews in your PR. See the examples below.
1. If you refactor some codes with changing classes, showing the class hierarchy will help reviewers.
2. If you fix some SQL features, you can provide some references of other DBMSes.
3. If there is design documentation, please add the link.
4. If there is a discussion in the mailing list, please add the link.
-->
### Why are the changes needed?
<!--
Please clarify why the changes are needed. For instance,
1. If you propose a new API, clarify the use case for a new API.
2. If you fix a bug, you can clarify why it is a bug.
-->
### Does this PR introduce _any_ user-facing change?
<!--
Note that it means *any* user-facing change including all aspects such as the documentation fix.
If yes, please clarify the previous behavior and the change this PR proposes - provide the console output, description, screenshot and/or a reproducable example to show the behavior difference if possible.
If possible, please also clarify if this is a user-facing change compared to the released Hive versions or within the unreleased branches such as master.
If no, write 'No'.
-->
### How was this patch tested?
added unit test
<!--
If tests were added, say they were added here. Please make sure to add some test cases that check the changes thoroughly including negative and positive cases if possible.
If it was tested in a way different from regular unit tests, please clarify how you tested step by step, ideally copy and paste-able, so that other reviewers can test and check, and descendants can verify in the future.
If tests were not added, please describe why they were not added and/or why it was difficult to add.
-->
----------------------------------------------------------------
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:
users@infra.apache.org
Issue Time Tracking
-------------------
Worklog Id: (was: 501509)
Remaining Estimate: 0h
Time Spent: 10m
> Configurations to delay the deletion of obsolete files by the Cleaner
> ---------------------------------------------------------------------
>
> Key: HIVE-24275
> URL: https://issues.apache.org/jira/browse/HIVE-24275
> Project: Hive
> Issue Type: New Feature
> Reporter: Kishen Das
> Priority: Major
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Whenever compaction happens, the cleaner immediately deletes older obsolete files. In certain cases it would be beneficial to retain these for certain period. For example : if you are serving the file metadata from cache and don't want to invalidate the cache during compaction because of performance reasons.
> For this purpose we should introduce a configuration hive.compactor.delayed.cleanup.enabled, which if enabled will delay the cleaning up obsolete files. There should be a separate configuration CLEANER_RETENTION_TIME to specify the duration till which we should retain these older obsolete files.
> It might be beneficial to have one more configuration to decide whether to retain files involved in an aborted transaction hive.compactor.aborted.txn.delayed.cleanup.enabled .
--
This message was sent by Atlassian Jira
(v8.3.4#803005)