[
https://issues.apache.org/jira/browse/HBASE-3904?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13050155#comment-13050155
]
Jean-Daniel Cryans commented on HBASE-3904:
-------------------------------------------
Creating createTableSync() wouldn't make much sense since the HBA.createTable()
methods are per their javadoc already synchronized with the creation of the
table. To me this means that they aren't respecting their contract so I
wouldn't worry about keeping backward compatibility.
About HCM.isTableAvailable, I'd think it's fine if it returns true even tho not
all regions are available in the case where the table creation wasn't completed
because the process was async. Because it's async.
> 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.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
