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

Anoop Sam John commented on HBASE-13147:
----------------------------------------

Just change the doc around HConstant#META_VERSION - It speaks abt keeping the 
META version in the ROOT table. Instead we (will) rely on the meta version 
which comes from the HTD attributes.

On a side note (not your patch) we have HConstants with 
@InterfaceAudience.Public. I don't think we will need to expose these constants 
to user. These are used internally by us for different reasons.  There might be 
other such constants also added to this. May be we will need another to Jira to 
clean up things. In the public exposed HConstant only keep things which need to 
be exposed.  For sharing common constants (which are not be public exposed) let 
us have another constants file.


bq.HTableDescriptor metaDescriptor = TableDescriptor.metaTableDescriptor(c)
This is still a static HTD. WHy?

Do we really need to add public APIs to HTD (which is client side public 
exposed)?  Can we deal with getValue() only?

> Load actual META table descriptor, don't use statically defined one.
> --------------------------------------------------------------------
>
>                 Key: HBASE-13147
>                 URL: https://issues.apache.org/jira/browse/HBASE-13147
>             Project: HBase
>          Issue Type: Bug
>          Components: master, regionserver
>    Affects Versions: 2.0.0
>            Reporter: Andrey Stepachev
>            Assignee: Andrey Stepachev
>         Attachments: HBASE-13147-branch-1.patch, 
> HBASE-13147-branch-1.v2.patch, HBASE-13147.patch, HBASE-13147.v2.patch, 
> HBASE-13147.v3.patch, HBASE-13147.v4.patch, HBASE-13147.v4.patch, 
> HBASE-13147.v5.patch, HBASE-13147.v6.patch, HBASE-13147.v7.patch
>
>
> In HBASE-13087 stumbled on the fact, that region servers don't see actual 
> meta descriptor, they use their own, statically compiled.
> Need to fix that.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to