[
https://issues.apache.org/jira/browse/HBASE-24609?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17213638#comment-17213638
]
Michael Stack commented on HBASE-24609:
---------------------------------------
bq. And the suggested name is InfoColumnFamilyFormat? It is on master only so
it is free to change the name at any time.
On above, I think CatalogColumnFamily would be better... Its used against root
and meta, now? And no need of the 'Format' since it Formats and Parses. Do you
think it will only ever write the 'info' family? If sure, add it in to the name
otherwise not.
Was worried that the CatalogColumnFamily is being spread about the code base;
i.e. a repeat of what MTA was doing. But maybe you are thinking that it ok
because CCF is just about formatting and parsing? And perhaps will eventually
be in two places only... the CMTA and RSS (perhaps thats what you are thinking?)
> 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)
