Mailing-List: contact notifications-help@accumulo.apache.org; run by ezmlm
Precedence: bulk
Reply-To: jira@apache.org
Date: Mon, 12 Aug 2013 22:21:48 +0000 (UTC)
From: "Sean Hickey (JIRA)" <jira@apache.org>
To: notifications@accumulo.apache.org
Message-ID: <JIRA.12611276.1349912970529.49883.1376346108650@arcas>
In-Reply-To: <JIRA.12611276.1349912970529@arcas>
References: <JIRA.12611276.1349912970529@arcas>
Subject: [jira] [Commented] (ACCUMULO-802) table namespaces
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Sean Hickey commented on ACCUMULO-802:
--------------------------------------

The patches above are well out of date. I've been working on github for a while, so [here's a link to my repo|https://github.com/Wisellama/accumulo] that I'm working on. This ticket is just the ACCUMULO-802 branch on my repo.
                
> table namespaces
> ----------------
>
>                 Key: ACCUMULO-802
>                 URL: https://issues.apache.org/jira/browse/ACCUMULO-802
>             Project: Accumulo
>          Issue Type: New Feature
>            Reporter: Eric Newton
>            Assignee: Sean Hickey
>             Fix For: 1.6.0
>
>         Attachments: ACCUMULO-802.v0.patch, ACCUMULO-802.v1.patch, ACCUMULO-802.v2.patch, ACCUMULO-802.v3.patch, ACCUMULO-802.v4.patch, ACCUMULO-802.v5.patch, table-namespaces-README.txt, table-namespaces-README.v1.txt, table-namespaces-README.v2.txt
>
>
> A large cluster is a valuable shared resource.  The current permission system and simple table naming structure does not allow for delegation of authority and safe partitioning within this shared resource.
> Use cases:
>  # create a namespace (like "test") and delegate the {{grant}} permission to tables created in that namespace to a user that would manage those tables. Presently, {{grant}} is never delegated.
>  # create simple "test" and "production" namespaces that are trivial for users to switch between.  For example, instead of having tables "test_index" and "test_documents" the client would support "index" and "documents" with an API to support switching trivially between the the different environments.
>  # create a set of tables in a namespace called "latest"  This namespace is re-created periodically with a map-reduce job.  If code changes inadvertently create a corrupt "latest," users can switch to the set of tables known as "safest"  In this way, users can experiment, and provide feedback on incremental improvements, while have a safe fallback.
>  # two applications hosted on the same cluster that can share a table, which has been "aliased" into their namespace.  Namespace-local permissions are ignored, but a (most likely read-only) view of the table is available.  This would be helpful for reference tables.
>  # quotas/priorities.  Implement namespace-specific priorities and resource allocations.  It is reasonable to run namespace-specific queries and ingest on production equipment. Large cluster resources are always limited, and often the *only* place where near-production quality software can be run at full scale.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira