[
https://issues.apache.org/jira/browse/HBASE-21154?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16604980#comment-16604980
]
stack commented on HBASE-21154:
-------------------------------
[~mdrob] One thought is that adding to hbase:meta schema is tough given its
hard-coded at the moment (to be fixed so we can split meta). Was thinking we
could put namespace in the new-to-branch-2 'table' column-family. Currently it
has a single column, 'table:state'. Could add a column 'table:namepace'. This
is an ugly hack but better than a table that hangs out in assignment purgatory.
> Remove hbase:namespace table; fold it into hbase:meta
> -----------------------------------------------------
>
> Key: HBASE-21154
> URL: https://issues.apache.org/jira/browse/HBASE-21154
> Project: HBase
> Issue Type: Improvement
> Components: meta
> Reporter: stack
> Priority: Major
>
> Namespace table is a small system table. Usually it has two rows. It must be
> assigned before user tables but after hbase:meta goes out. Its presence
> complicates our startup and is a constant source of grief when for whatever
> reason, it is not up and available. In fact, master startup is predicated on
> hbase:namespace being assigned and will not make progress unless it is up.
> Lets just add a new 'ns' column family to hbase:meta for namespace.
> Here is a default ns table content:
> {code}
> hbase(main):023:0* scan 'hbase:namespace'
> ROW
> COLUMN+CELL
> default
> column=info:d, timestamp=1526694059106,
> value=\x0A\x07default
> hbase
> column=info:d, timestamp=1526694059461,
> value=\x0A\x05hbase
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
