[
https://issues.apache.org/jira/browse/HBASE-8963?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13941345#comment-13941345
]
bharath v commented on HBASE-8963:
----------------------------------
Thanks for your comments everyone. It makes sense to add a per table config.
Will write a patch for that.
[~enis] We run these files through all the configured cleaners, which checks
all the back links/snapshots associated hfiles and deletes only if its valid.
So that case is covered.
The motivation for a global flag is probably if someone wants to apply it for
all the tables and not go through the pain of setting it per table. They can
override specific tables with {SKIP_ARCHIVE = false} in which case, the global
parameter isn't taken into consideration.
> Add configuration option to skip HFile archiving
> ------------------------------------------------
>
> Key: HBASE-8963
> URL: https://issues.apache.org/jira/browse/HBASE-8963
> Project: HBase
> Issue Type: Improvement
> Reporter: Ted Yu
> Assignee: bharath v
> Fix For: 0.99.0
>
> Attachments: HBASE-8963.trunk.v1.patch, HBASE-8963.trunk.v2.patch,
> HBASE-8963.trunk.v3.patch, HBASE-8963.trunk.v4.patch,
> HBASE-8963.trunk.v5.patch, HBASE-8963.trunk.v6.patch,
> HBASE-8963.trunk.v7.patch
>
>
> Currently HFileArchiver is always called when a table is dropped.
> A configuration option (either global or per table) should be provided so
> that archiving can be skipped when table is deleted.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
