accumulo-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Christopher Tubbs (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (ACCUMULO-1907) Prevent moving tables between namespaces
Date Tue, 19 Nov 2013 13:43:21 GMT

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

Christopher Tubbs commented on ACCUMULO-1907:
---------------------------------------------

I agree it could be a nice feature. However, it's not just documentation of behavior. It's
also implementation concerns, and the introduction of bugs by swapping out the parent of a
table configuration in the configuration hierarchy.

It's not an essential part of this feature. We can always add it later.

Besides, you can achieve the same effect, but with more well-defined behavior by cloning a
table across namespaces. (It's more well-defined, because the new table will never inherit
from the old configuration... only the new one, from the moment it comes online.)

> 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