[
https://issues.apache.org/jira/browse/ACCUMULO-3236?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Christopher Tubbs resolved ACCUMULO-3236.
-----------------------------------------
Resolution: Won't Fix
Doesn't look like this is going to go anywhere. If needed, can re-open at
https://github.com/apache/accumulo/issues
> 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
> Assignee: John Vines
> Priority: Major
>
> 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
(v7.6.3#76005)
