[
https://issues.apache.org/jira/browse/HBASE-24609?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17213379#comment-17213379
]
Michael Stack commented on HBASE-24609:
---------------------------------------
A few questions after looking at this (belatedly)....
Why move MetaTableAccessor to hbase-balancer? The accessor seems more general
than balancing affairs only. Class is described as
bq. Read/write operations on <code>hbase:meta</code> region as well as
assignment information stored
bq. * to <code>hbase:meta</code>.
The 'hbase-balancer' is described as ' <description>HBase Balancer
Support</description>'
The rename of asyncmetatableaccessor to clientmetatableaccessor looks good but
I'm unclear on when clientmetatableaccessor and when metatableaccessor? The
clientmetatableaccessor is described like the metatableaccessor.
bq. * The (asynchronous) meta table accessor used at client side. Used to
read/write region and
bq. * assignment information store in <code>hbase:meta</code>.
Previous I used MTA to write hbase:meta. Now I use CMTA too or exclusively?
What you thinking?
s/CatalogFamilyFormat/CatalogColumnFamily/? Or CatalogColumnFamilyParser? Will
this class cover the 'info' columnfamily only? Or you foresee it doing other
columnfamilies too?
Why we need it as standalone class that is making an appearance in a few places
around the code base? It was an internal affair of MetaTableAccessor previously?
Thanks
> Move MetaTableAccessor out of hbase-client
> ------------------------------------------
>
> Key: HBASE-24609
> URL: https://issues.apache.org/jira/browse/HBASE-24609
> Project: HBase
> Issue Type: Task
> Components: amv2, Client, meta
> Reporter: Duo Zhang
> Assignee: Duo Zhang
> Priority: Major
> Fix For: 3.0.0-alpha-1
>
>
> On master branch we have AsyncMetaTableAccessor which is used at client side
> and MetaTableAccessor has lots of internal methods for implementing
> assignment, which is not part of our client code.
> So let's move it to hbase-server, and in the future, maybe in hbase-balancer?
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
