Mailing-List: contact notifications-help@accumulo.apache.org; run by ezmlm
Precedence: bulk
Reply-To: jira@apache.org
Date: Fri, 17 Oct 2014 06:26:34 +0000 (UTC)
From: "Christopher Tubbs (JIRA)" <jira@apache.org>
To: notifications@accumulo.apache.org
Message-ID: <JIRA.12748384.1413400650000.284398.1413527194317@Atlassian.JIRA>
In-Reply-To: <JIRA.12748384.1413400650000@Atlassian.JIRA>
References: <JIRA.12748384.1413400650000@Atlassian.JIRA>
 <JIRA.12748384.1413400650044@arcas>
Subject: [jira] [Comment Edited] (ACCUMULO-3236) Clone table into an
 existing table
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/ACCUMULO-3236?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14174765#comment-14174765 ] 

Christopher Tubbs edited comment on ACCUMULO-3236 at 10/17/14 6:25 AM:
-----------------------------------------------------------------------

I agree it's definitely more similar (semantically, not implementation-wise) to bulk import. The bulk import command is importDirectory(). Perhaps importFromTable(). Snapshot sort of implies that the table is consistent at a point in time, and I don't think we can guarantee that unless the source table is offline'd first. Is that going to be a prerequisite for this?


was (Author: ctubbsii):
I agree it's definitely more similar (semantically, not implementation-wise) to bulk import. The bulk import command is importDirectory(). Perhaps importFromTable()?

> 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
>             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
(v6.3.4#6332)