You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@hbase.apache.org by "Dong0829 (Jira)" <ji...@apache.org> on 2022/07/27 02:28:00 UTC

[jira] [Updated] (HBASE-27245) Expose the archive option to end user

     [ https://issues.apache.org/jira/browse/HBASE-27245?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Dong0829 updated HBASE-27245:
-----------------------------
    Description: 
For the delete table procedure, we already have archive option, but the archive now will already be true and not provided to end user.

Actually its valuable to provide this option to the end user because some time, customer does not want this table archived when drop the table, it will waste the storage and time if hbase keep archive the table. Especially for the users who are using AWS s3 or Azure as storage which will take lots time for the rename and delete operation for big tables

  was:
For the delete table procedure, we already have archive option, but the archive now will already be true and not provided to end user.

Actually its valuable to provide this option to the end user because some time, customer does not want this table archived when drop the table, it will waste the storage and time if hbase keep archive the table. Especially for the users who are using AWS s3 or Azure as storage which will take more time for the rename and delete operation


> Expose the archive option to end user
> -------------------------------------
>
>                 Key: HBASE-27245
>                 URL: https://issues.apache.org/jira/browse/HBASE-27245
>             Project: HBase
>          Issue Type: New Feature
>          Components: master
>    Affects Versions: 2.5.0
>            Reporter: Dong0829
>            Priority: Minor
>
> For the delete table procedure, we already have archive option, but the archive now will already be true and not provided to end user.
> Actually its valuable to provide this option to the end user because some time, customer does not want this table archived when drop the table, it will waste the storage and time if hbase keep archive the table. Especially for the users who are using AWS s3 or Azure as storage which will take lots time for the rename and delete operation for big tables



--
This message was sent by Atlassian Jira
(v8.20.10#820010)