[
https://issues.apache.org/jira/browse/HBASE-1758?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12742899#action_12742899
]
Vaibhav Puranik commented on HBASE-1758:
----------------------------------------
We have removed region awareness (methods such as getTableRegions etc) from the
HTableInterface to simplify it. (As most of the clients won't really need it).
There is one class in Stargate - RegionResource. This class has a method -
getTableRegions. We think that the method is just exposing
HTable.getTableRegions through the REST interface.
Now that we have removed getTableRegions from the HTableInterface, I think that
this class RegionResource should be deleted.
Andy, can you please comment? Is RegionResource really needed?
> Extract interface out of HTable
> -------------------------------
>
> Key: HBASE-1758
> URL: https://issues.apache.org/jira/browse/HBASE-1758
> Project: Hadoop HBase
> Issue Type: Improvement
> Components: client
> Reporter: Vaibhav Puranik
> Fix For: 0.21.0
>
> Attachments: HTableInterface.patch
>
>
> As per discussions in Hackathon, we have extracted interface out of HTable
> and named it as HTableInterface. This will make unit testing client code
> easier and simplify client API.
> It opens other possibilities such as creating a HTable that does not do any
> RPC calls, MockHTable etc.
> HTablePool still returns HTable instances. But we have added a setter method
> for HTableInterfaceFactory on it. Thus developers can write their own
> HTableInterfaceFactory impl to return their own HTableInterface
> implementation.
> I have assigned this issue to 0.21 but you may consider it to move it to 0.20
> if possible.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
