accumulo-notifications mailing list archives

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


Christopher Tubbs commented on ACCUMULO-3236:

Maybe "copyRange(fromTable, toTable)" is the appropriate context, then (with "copy" being
the verb)? Perhaps "clone" is just not the appropriate verb? (And perhaps this isn't so much
an extension of the existing clone feature, but an entirely new primitive operation?)

As for the 571 comment, I'm wouldn't consider union to be destructive (I certainly wasn't
thinking that it would be, since that's not true in the analogous SQL syntax I referred to),
but I see now that the "merge" language could imply that. I wouldn't think the destruction
is needed, though, since we have delete already.

> 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