Return-Path: X-Original-To: apmail-accumulo-notifications-archive@minotaur.apache.org Delivered-To: apmail-accumulo-notifications-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 3589F173C7 for ; Wed, 15 Oct 2014 18:18:34 +0000 (UTC) Received: (qmail 92153 invoked by uid 500); 15 Oct 2014 18:18:34 -0000 Delivered-To: apmail-accumulo-notifications-archive@accumulo.apache.org Received: (qmail 92112 invoked by uid 500); 15 Oct 2014 18:18:34 -0000 Mailing-List: contact notifications-help@accumulo.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: jira@apache.org Delivered-To: mailing list notifications@accumulo.apache.org Received: (qmail 91990 invoked by uid 99); 15 Oct 2014 18:18:33 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 15 Oct 2014 18:18:33 +0000 Date: Wed, 15 Oct 2014 18:18:33 +0000 (UTC) From: "John Vines (JIRA)" To: notifications@accumulo.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (ACCUMULO-571) Merge table into existing table MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/ACCUMULO-571?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Vines updated ACCUMULO-571: -------------------------------- Fix Version/s: 1.7.0 > Merge table into existing table > ------------------------------- > > Key: ACCUMULO-571 > URL: https://issues.apache.org/jira/browse/ACCUMULO-571 > Project: Accumulo > Issue Type: New Feature > Components: client, tserver > Reporter: John Vines > Assignee: John Vines > Labels: gsoc2013, mentor > Fix For: 1.7.0 > > > This is idea that was recently brought to my attention. The use case is a user wants to essentially clone a subset of a table into an existing table. Currently cloning does not allow this. Current option is to copy the files in hdfs and then bulk import, since bulk import moves the files. This is pretty wasteful. Under the hood, the system can handle the cross-linking between files like that. We just need a mechanism to provide the ability to assign a subset of data to another region. > Potential uses include the above mentioned, as well as the potential for users to bring fresh data into a table which was cloned and modified. There may be other cases, but I haven't fully thought out this problem space. > The biggest problem with this is it does put the onus on the user for ensuring that data in the in memory maps is flushed before moving, as well as for handling the possibility of duplicate data. -- This message was sent by Atlassian JIRA (v6.3.4#6332)