[
https://issues.apache.org/jira/browse/HBASE-10208?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
rajeshbabu resolved HBASE-10208.
--------------------------------
Resolution: Fixed
bq. High-level we want to hide notion of 'region' from clients. Does this
change go against such an axiom?
Yes Its looks like against to that.
bq. Code requiring these special methods could check whether an HTI is an
HTable and cast accordingly. That way we won't tie the interface to
implementation details. Would that work for you rajeshbabu?
That works for me.
Sorry for the mess. Closing this issue as invalid.
Thanks.
> Add split keys and region location related API in HTable to HTableInterface
> as well
> -----------------------------------------------------------------------------------
>
> Key: HBASE-10208
> URL: https://issues.apache.org/jira/browse/HBASE-10208
> Project: HBase
> Issue Type: Bug
> Components: Client
> Reporter: rajeshbabu
> Assignee: rajeshbabu
> Fix For: 0.99.0
>
>
> These are APIs related to split keys avaiable in HTable same can be to HTI
> getStartKeys()
> getEndKeys()
> getStartEndKeys()
> getSplitKeys() - New
> and 3 more APIs related to find region location when we specify row also can
> be added to HTI
> getRegionLocation(final String row)
> getRegionLocation(final byte [] row)
> getRegionLocation(final byte [] row, boolean reload)
--
This message was sent by Atlassian JIRA
(v6.1.4#6159)
