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

Enis Soztutar commented on HBASE-7999:
--------------------------------------

bq. The advantage here is that its pretty simple and already written
Agreed. We can go with this and revisit the implementation once we have 
namespaces. The only thing is that we are exposing some of the stuff (like 
list_system_tables, list table rpc, etc). If we resolve HBASE-8015, there won't 
be any need for those. 
                
> 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

Reply via email to