[
https://issues.apache.org/jira/browse/HBASE-8963?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13962567#comment-13962567
]
Lars Hofhansl commented on HBASE-8963:
--------------------------------------
bq. I think Lars is right that making "hbase.master.hfilecleaner.ttl"
configurable per table
It's not actually as simple as I thought. At the time we're archiving/deleting
HFiles we do not necessarily have access to the table's metadata, it's
expensive to read the table description (in the region or family case). When
the table is dropped, we'd need to keep the TTL information somewhere else.
> 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, HBASE-8963.trunk.v8.patch,
> HBASE-8963.trunk.v9.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)
