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

Sean Busbey commented on HBASE-23055:
-------------------------------------

bq. Or let's open a follow on issue, and set it as a blocker of 2.3.0, to 
finish the altering meta change, but persisting the state of meta table, and 
implement alter the alter meta table procedure.

we're overdue on the 2.3.z release line starting. an issue for dev@, but maybe 
we should start RCs off an earlier point in the branch-2 history.

> Alter hbase:meta
> ----------------
>
>                 Key: HBASE-23055
>                 URL: https://issues.apache.org/jira/browse/HBASE-23055
>             Project: HBase
>          Issue Type: Task
>            Reporter: Michael Stack
>            Assignee: Michael Stack
>            Priority: Major
>             Fix For: 3.0.0, 2.3.0
>
>
> hbase:meta is currently hardcoded. Its schema cannot be change.
> This issue is about allowing edits to hbase:meta schema. It will allow our 
> being able to set encodings such as the block-with-indexes which will help 
> quell CPU usage on host carrying hbase:meta. A dynamic hbase:meta is first 
> step on road to being able to split meta.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to