accumulo-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "John Vines (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (ACCUMULO-571) Merge table into existing table
Date Wed, 15 Oct 2014 19:15:34 GMT

     [ https://issues.apache.org/jira/browse/ACCUMULO-571?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

John Vines updated ACCUMULO-571:
--------------------------------
    Assignee:     (was: John Vines)

> 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
>              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)

Mime
View raw message