accumulo-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF subversion and git services (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (ACCUMULO-1906) Remove namespace operations that operate on the tables they contain
Date Thu, 05 Dec 2013 00:00:36 GMT

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

ASF subversion and git services commented on ACCUMULO-1906:
-----------------------------------------------------------

Commit 3c920943bf92e2c15a5eeb4945165b3573003f33 in branch refs/heads/master from [~ctubbsii]
[ https://git-wip-us.apache.org/repos/asf?p=accumulo.git;h=3c92094 ]

ACCUMULO-1906 Remove ops on tables in a namespace

  Removing operations on tables in a namespace where the same operation
  can be easily accomplished with a short sequence of API calls on
  existing methods. Also, clean up Javadocs.


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

Mime
View raw message