You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@accumulo.apache.org by "Christopher Tubbs (JIRA)" <ji...@apache.org> on 2013/11/18 22:31:21 UTC
[jira] [Commented] (ACCUMULO-1906) Remove namespace operations that
operate on the tables they contain
[ https://issues.apache.org/jira/browse/ACCUMULO-1906?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13825797#comment-13825797 ]
Christopher Tubbs commented on ACCUMULO-1906:
---------------------------------------------
This also includes clone namespaces.
> Remove namespace operations that operate on the tables they contain
> -------------------------------------------------------------------
>
> Key: ACCUMULO-1906
> URL: https://issues.apache.org/jira/browse/ACCUMULO-1906
> Project: Accumulo
> Issue Type: Sub-task
> Components: client, master, tserver
> Reporter: Christopher Tubbs
> Fix For: 1.6.0
>
>
> Operations like "delete namespace", with the force flag set to true, and "offline namespace", first operate on all the tables they contain. These introduce a lot of complexity and concurrency issues that are difficult to reason about and explain via simple API calls, which could result in unexpected behavior for users.
> These features aren't needed for an initial implementation, and don't add significant value to warrant their risk at this time. Users can use the basic operations already provided ({{namespaceOps.listTables() + tableOps.delete(table)}}) to achieve more predictable behavior in client code, where actions are more easy to reason about.
--
This message was sent by Atlassian JIRA
(v6.1#6144)