[
https://issues.apache.org/jira/browse/HBASE-23055?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17012871#comment-17012871
]
Duo Zhang commented on HBASE-23055:
-----------------------------------
Replied on RB, I still do not think this is a good solution. We should design
for the future, for splittable meta, not for a temporary solution. And I do not
get the point why we jsut make the state for meta table volatile, why not just
store it on zk?
And when reviewing the patch, a good thing is that, we do not reference the
meta table descriptor everywhere in the code. We just reference the region info
everywhere, which I think it is OK for now as the region info does not include
the table descriptor. This can be done in the future when implementing
splittable meta.
So I think we could get the patch in on master, or even on branch-2, but not
the current one...
Thanks.
> 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)
