[
https://issues.apache.org/jira/browse/HBASE-22578?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16894946#comment-16894946
]
Anoop Sam John commented on HBASE-22578:
----------------------------------------
When a table created or alter with the table level config turned ON for the
snapshot scanning feature, do we check this config also and see whether the
required cleaner is also been set? If not set can we fail that op? Anyways
even if we succeed the op, the behave may be unpredictable depending on whether
a possible HFileCleaner run cleaned up the dir or not.
Whether the HFileCleaner itself could have made aware abt the table config of
supporting the snapshot scan? So this exta config need was not needed? Sorry
for asking too late.
So when this cleaner also in use, it wont delete any of the empty dir
irrespective of whether snapshot scan is enabled on that particular table or
not. Correct?
> HFileCleaner should not delete empty ns/table directories used for user san
> snapshot feature
> --------------------------------------------------------------------------------------------
>
> Key: HBASE-22578
> URL: https://issues.apache.org/jira/browse/HBASE-22578
> Project: HBase
> Issue Type: Sub-task
> Reporter: Yi Mei
> Assignee: Yi Mei
> Priority: Major
> Fix For: 3.0.0, 2.3.0
>
>
> HBASE-21995 add a coprocessor to set HDFS acls for HBase users who own HBase
> read permission to mask users have the ability to scan snapshot directly.
> It creates empty directories for namespace and table under archive directory
> and set HDFS acls to these directories after namespace or table is created,
> in this way, users can read files under archive directory.
> But the HFileCleaner will delete empty directories and this will break this
> feature. So if the user scan snapshot feature is enabled, HFileCleaner should
> not delete empty ns/table directories.
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
