You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Ted Yu (JIRA)" <ji...@apache.org> on 2011/07/09 01:56:17 UTC

[jira] [Resolved] (HBASE-3904) HConnection.isTableAvailable returns true even with not all regions available.

     [ https://issues.apache.org/jira/browse/HBASE-3904?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Ted Yu resolved HBASE-3904.
---------------------------

      Resolution: Fixed
    Release Note: 
HBA.createTable(final HTableDescriptor desc, byte [][] splitKeys)
is synchronous. Use this method instead of creating table asynchronously followed by call to HConnection.isTableAvailable().
    Hadoop Flags: [Reviewed]

I am closing this JIRA as there lacks consensus how HConnection.isTableAvailable() should be implemented for table which was created asynchronously.

> 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
>            Assignee: Ted Yu
>            Priority: Minor
>         Attachments: 3904-v3.txt, 3904-v4.txt, 3904-v5.txt, 3904.txt
>
>
> 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