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 14:17:34 GMT


John Vines commented on ACCUMULO-3236:

Your way is not the same. Your way involves interrupting all query and ingest to the destination
table because otherwise 
A. ingest could get out of sync or
B. queries are wrong because they were started on a table that is deleted.

I want a way to add the data in Table B to Table A without breaking running operations against
Table A. Any time you do a rename, that guarantee is broken and that is unacceptable to me.
I don't care about API primitives, I care about usability and the union method lacks 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