[ACCUMULO-802] table namespaces

• Type: New Feature
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 1.6.0
• Component/s: client, master, tserver
• Assignee: Sean Hickey
• Reporter: Eric C. Newton
• Created: 10/Oct/12 23:49
• Updated: 19/Oct/15 21:50
• Resolved: 16/Dec/13 18:38

Description

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:

1. 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.
2. 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.
3. 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.
4. 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.
5. 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.

Issue Links

• is depended upon by: ACCUMULO-1712 Remove special characters from path names of metadata tables
• is depended upon by: ACCUMULO-324 System/site constraints and iterators should NOT affect the METADATA table
• is related to: ACCUMULO-617 default access for a table
• is related to: ACCUMULO-1865 Implement table namespace clone in MockAccumulo
• is related to: ACCUMULO-2885 User manual does not define what namespaces are or how they work
• relates to: ACCUMULO-4035 Spurious NamespacesIT.verifyConstraintInheritance failure
• links to: ReviewBoard

Sub-Tasks

• Create per-user permissions for a given table namespace: Resolved
• Put provided tables in their own (system) namespace: Resolved
• Create node in per-table configuration hierarchy for table namespaces: Resolved
• Remove namespace operations that operate on the tables they contain: Resolved
• Prevent renaming tables between namespaces: Resolved
• Clone table has race condition when excluding namespace properties: Resolved
• Should not be able to create table in system namespace (accumulo): Resolved
• Potential deadlock with namespace reservations in clone table fate operation: Resolved
• Tables utility should explain which table failed if the regex fails: Resolved
• default namespace name should be part of the public api: Resolved