[
https://issues.apache.org/jira/browse/HBASE-7999?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13595552#comment-13595552
]
Jesse Yates commented on HBASE-7999:
------------------------------------
I'd argue that we should still reserve a system namespace (the same is already
discussed in HBASE-8015), so keeping these special system labels around isn't
all that far fetched. The actual list table rpc would change, but other than
that much of the higher-level things would remain very similar (e.g. ui, shell,
etc) to support the system tooling separate from the regular namespace (to help
avoid accidental changes to internal tables)
> Add 'system' tables
> -------------------
>
> Key: HBASE-7999
> URL: https://issues.apache.org/jira/browse/HBASE-7999
> Project: HBase
> Issue Type: Sub-task
> Components: Client, master, Protobufs
> Reporter: Jesse Yates
> Assignee: Jesse Yates
> Fix For: 0.96.0
>
> Attachments: hbase-7999-v0.patch, hbase-7999-v2.patch
>
>
> System tables are necessary as we start moving towards other internally
> scoped uses for tables (already we have a similar paradigm with the ACL table
> in the security stuff). This allows things like an statistics table, a
> secondary index table, moving replication queues out of ZK - just to name a
> couple of things that have come up.
> The first use-case would be HBASE-7958 where we would want to support a
> system level statistics table.
--
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
