accumulo-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Adam Fuchs (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (ACCUMULO-1907) Prevent moving tables between namespaces
Date Mon, 18 Nov 2013 23:33:22 GMT

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

Adam Fuchs commented on ACCUMULO-1907:
--------------------------------------

[~ctubbsii] Seems like moving tables between namespaces could be a nice feature. For example
a table could be created in one namespace and then "published" by moving it to another namespace.
What are some examples of configuration changes that can cause a problem in table migration,
and can we possibly address this by documentation?

> Prevent moving tables between namespaces
> ----------------------------------------
>
>                 Key: ACCUMULO-1907
>                 URL: https://issues.apache.org/jira/browse/ACCUMULO-1907
>             Project: Accumulo
>          Issue Type: Sub-task
>          Components: client, master, tserver
>            Reporter: Christopher Tubbs
>            Assignee: Christopher Tubbs
>             Fix For: 1.6.0
>
>
> Moving tables between namespaces is risky, because of the sudden change of inheritance
from the configuration. This could introduce a lot of unexpected behavior. To avoid this,
we should just prevent moving between namespaces for now. This feature can be added at a later
date if it becomes highly demanded, sufficiently to warrant addressing the unique concurrency
considerations.



--
This message was sent by Atlassian JIRA
(v6.1#6144)

Mime
View raw message