[ https://issues.apache.org/jira/browse/HBASE-20243?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16411105#comment-16411105 ]
Appy edited comment on HBASE-20243 at 3/23/18 9:56 AM: ------------------------------------------------------- bq. I think it would be more convenient if we had a command to clone the table directly. i think so too. Edit: Because in one-off or evolving cases, unlike set pattern as you guys have, the only other way i can think of is snapshot + clone + truncate which is too many steps. (Or is there a another better way?) But the command name sure is confusing, given what 'clone' has meant historically in hbase world; cloning a snapshot means both schema + data gets copied. Can we please rename it to cloneTableSchema? was (Author: appy): bq. I think it would be more convenient if we had a command to clone the table directly. i think so too. But the command name sure is confusing, given what 'clone' has meant historically in hbase world; cloning a snapshot means both schema + data gets copied. Can we please rename it to cloneTableSchema? > [Shell] Add shell command to create a new table by cloning the existent table > ----------------------------------------------------------------------------- > > Key: HBASE-20243 > URL: https://issues.apache.org/jira/browse/HBASE-20243 > Project: HBase > Issue Type: Improvement > Components: shell > Reporter: Guangxu Cheng > Assignee: Guangxu Cheng > Priority: Minor > Fix For: 2.1.0 > > Attachments: HBASE-20243.master.001.patch > > > In the production environment, we need to create a new table every day. The > schema and the split keys of the table are the same as that of yesterday's > table, only the name of the table is different. For example, > xxxxx_20180321,xxxxx_20180322 etc.But now there is no convenient command to > do this. So we may need such a command(clone_table) to create a new table by > cloning the existent table. -- This message was sent by Atlassian JIRA (v7.6.3#76005)