[
https://issues.apache.org/jira/browse/HBASE-4548?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13122369#comment-13122369
]
Jonathan Hsieh commented on HBASE-4548:
---------------------------------------
@Todd, (also posted in HBASE-4377).
I think there is some confusion. Clients do not directly access hdfs. Let me
add more detail.
In trunk post HBASE-451, the HMaster reads and caches data from the file system
(not the client). It then serves this the HTableDescriptors to the client rpc's
via HConnectionManager to talk to the HMaster which just ships the cached HTD
data.
HMaster on initialization reads file system for HTD data.
Client calls listTables() -> HMaster (serve cached data from file system).
Pre-HBASE-451, it the client HConnectionManager does a meta scan and builds
HTableDescriptors.
Client calls listTables() which actually is a metascan and that builds htds.
> Client should not look on HDFS to list tables
> ---------------------------------------------
>
> Key: HBASE-4548
> URL: https://issues.apache.org/jira/browse/HBASE-4548
> Project: HBase
> Issue Type: Bug
> Components: client
> Affects Versions: 0.92.0
> Reporter: Todd Lipcon
> Priority: Critical
> Fix For: 0.92.0
>
>
> In HBASE-4377, Jon noticed that HConnectionManager.listTable now looks on
> HDFS for the table list. This seems incorrect, since the client may not have
> access to the hbase directory on HDFS (eg in a secure cluster). At the least,
> it should RPC to the master to find a table list, and have the master do the
> list on HDFS.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
