[
https://issues.apache.org/jira/browse/HBASE-3904?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13036678#comment-13036678
]
stack commented on HBASE-3904:
------------------------------
So, how do you think this should work Vidhya? isTableAvailable won't ever know
how many regions there are supposed to be in a table. Checking for > 0 is
probably the best it could ever do. It sounds to me like we need something
else or that after isTableAvailable returns true, that then you should get an
HTable instance and call
http://hbase.apache.org/apidocs/org/apache/hadoop/hbase/client/HTable.html#getRegionsInfo()
in a loop with a bit of wait until the number of regions comes up to close the
number you passed to create table? (FYI: I haven't tried this to see if it
will work).
> HConnection.isTableAvailable returns true even with not all regions available.
> ------------------------------------------------------------------------------
>
> Key: HBASE-3904
> URL: https://issues.apache.org/jira/browse/HBASE-3904
> Project: HBase
> Issue Type: Bug
> Components: client
> Reporter: Vidhyashankar Venkataraman
> Priority: Minor
>
> This function as per the java doc is supposed to return true iff "all the
> regions in the table are available". But if the table is still being created
> this function may return inconsistent results (For example, when a table with
> a large number of split keys is created).
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
