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

Michael Stack commented on HBASE-23055:
---------------------------------------

bq. I still think we'd better land this on a feature branch first?

Because you want to run a vote before it gets merged?

bq. This is a very critical change as we used to assume that the meta 
descriptor can not be changed.

That it can be changed is a minor affair? It should be changeable, no? Will 
anyone even notice? Unless you go out of your way, meta is as it always was. 
Only a few of us will note its changeable. Fewer will make use of the feature. 
Meantime it allows experimenting with meta schema -- a bottleneck -- and is a 
paving stone on our way to other features (splitting meta).

I'm having trouble understanding how this feature is problematic but we are 
fine w/ totally changing the procedure storage implementation in new minor 
release.

I could put it behind a big ON/OFF switch with default OFF though reluctant, as 
we have enough of those already with features on other side of the ON/OFF 
switch rotting for want of usage.

bq. I think you can port this feature to your internal branch first to see if 
it works well but for the official repo, we'd better not do this at this time, 
at least do not on branch-2?

I am trying to run upstream locally.

On adding it only to master branch for hbase3, I don't want to wait a year 
before this is in a shipping hbase.

> 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