[ https://issues.apache.org/jira/browse/ACCUMULO-3236?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14175106#comment-14175106 ]
John Vines commented on ACCUMULO-3236: -------------------------------------- I don't see why it has to be offline.Clone table doesn't require it to be offline. I was working with this being under the same contract - you get what you get when you call and if you want guaranteed data, you need to pause your ingest. We can keep the force flush flag though. > Clone table into an existing table > ---------------------------------- > > Key: ACCUMULO-3236 > URL: https://issues.apache.org/jira/browse/ACCUMULO-3236 > Project: Accumulo > Issue Type: Improvement > Components: client, tserver > Reporter: John Vines > Fix For: 1.7.0 > > > Currently we have the ability to clone a table, which takes all files > belonging to an existing table and then makes them owned by a second, brand > new table. I think there is a logic extension to this where you can add the > files to an already existing table. > One point of concern is if data is unused in existing files due to major > compactions of the shared files in the source table. This can be mitigated by > either chopping the files (which sorta goes against the idea of cloning) or > ensuring that at source table splits exist in the destination table. -- This message was sent by Atlassian JIRA (v6.3.4#6332)