accumulo-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "John Vines (JIRA)" <>
Subject [jira] [Commented] (ACCUMULO-3236) Clone table into an existing table
Date Wed, 15 Oct 2014 20:33:34 GMT


John Vines commented on ACCUMULO-3236:

I'm avoiding the word copy. The entire reason for this is to avoid copying data in order to
make it available to the destination source. We have clone, it has a known meaning, and that
meaning is the most appropriate for this operation.

And I'm avoiding the nuances of special casing of subsets of a table. This ticket is about
a first, simpler pass, which can be refined upon to provide things like sub-ranges.

Please provide that clarity in 571, as it was confusion there that lead to one of the reasons
for this ticket. I main for the reasons above that 571 at most an extension of this.

> Clone table into an existing table
> ----------------------------------
>                 Key: ACCUMULO-3236
>                 URL:
>             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

View raw message