[
https://issues.apache.org/jira/browse/KUDU-3326?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17835750#comment-17835750
]
ASF subversion and git services commented on KUDU-3326:
-------------------------------------------------------
Commit 44f4b930a8c2a4babc41870678683845694f3975 in kudu's branch
refs/heads/branch-1.17.x from kedeng
[ https://gitbox.apache.org/repos/asf?p=kudu.git;h=44f4b930a ]
KUDU-3326 correct error messages in tool usage instructions
This patch mainly fixes the error messages in the recall tool as follows:
`
Usage: kudu table recall <master_addresses> <tablet_id> [-new_table_name=<name>]
`
We expect to recall tables in soft delete state using the table ID,
not the tablet ID. The correct output is as follows:
`
Usage: kudu table recall <master_addresses> <table_id> [-new_table_name=<name>]
`
This is just about correcting the errors in the prompts and does not
involve any related recall logic. Therefore, there are no additional
unit tests added.
Change-Id: Ib1c6df0806eee78280b00f6a528d42d434a63e2f
Reviewed-on: http://gerrit.cloudera.org:8080/21266
Reviewed-by: Alexey Serbin <[email protected]>
Tested-by: Alexey Serbin <[email protected]>
(cherry picked from commit d06f35db2e5a0e93a3dcab0d3b26e4443914df89)
Reviewed-on: http://gerrit.cloudera.org:8080/21273
Reviewed-by: Yingchun Lai <[email protected]>
> Add Soft Delete Table Supports
> ------------------------------
>
> Key: KUDU-3326
> URL: https://issues.apache.org/jira/browse/KUDU-3326
> Project: Kudu
> Issue Type: New Feature
> Components: api, CLI, client, master, test
> Reporter: dengke
> Assignee: dengke
> Priority: Major
>
> h2. Brief description：
> Soft delete means that the kudu system will not delete the table
> immediately after receiving the command to delete the table. Instead, it will
> mark the table and set a validity period. After the validity period, will try
> again to determine whether the table really needs to be deleted.
> This feature can restore data conveniently and timely in the case of
> accidental deletion.
> h2. Relevant modification points：
> 1. After deleting a table, the original table name will be renamed as
> KUDU_TRASHED: < timestamp >: < original table name >, which becomes a trash
> table.
> 2. The contents of the trash table are exactly the same as those of the
> original table. Although it cannot be renamed, added or deleted directly,
> it can be read and written normally. The trash table will be retained for a
> period of time by default (such as 7 days, which can be modified through
> parameters). The compact priority of the trash table will be set to the
> lowest to save the system resources.
> 3. The master needs to add a thread to process expired trash tables and
> perform real deletion.
> 4. It is allowed to create a table with the same name as the original table,
> and the newly created table with the same name can be deleted normally.
> 5. It is allowed to recall deleted tables, but the following two situations
> cannot be recalled: the same original table name exists and the trash table
> has expired.
> 6. The KUDU_TRASHED is a reserved string for the system. Users are not
> allowed to create a table with table names starting with KUDU_TRASHED.
> 7. Kudu tool adaptation soft deletion.
> 8. Java API adaptation soft deletion.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
