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 Thu, 16 Oct 2014 03:06:33 GMT


John Vines commented on ACCUMULO-3236:

No, 571 specifies the ability to function against a subset of the source table. That is what
I'm avoiding.

And I, as an accumulo user, want all of the data in table B to exist in both table B and table
A. I don't want to create table C which I now need to worry about. If I wanted table C, I
can just as easily achieve that result by cloning A to B and then cloning B into C. By forcing
this ticket into a union function, I lose the basic functionality I want. But if implemented
as an operation which does alter the destination table, I could achieve the same results in
two steps.

The critical aspect of this feature request is:
I have table A
I have table B
I want the contents of table B to exist in table A
I still want table B to exist

Currently, my only option is to copy all of the contents of B and then bulk import, which
is wasteful. We have logic for cloning tables into a new destination by referencing the same
files. I want that same logic to be used to apply existing files to existing tablets so I
do not have to copy it.

> 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