I'm done with the update. I have implemented HRegionInfo.getStartKey
to remove the loop in locateRegion(final byte regionName). Tests are
running and so far, so good. I will update the JIRA when the tests
will be done.
2013/1/3, Jean-Marc Spaggiari <[EMAIL PROTECTED]>:
> I found HRegionInfo.getTableName(regionName) to get the table name
> quickly. Still searching for the startKey.
> HRegionInfo.getStartKey(regionName) doesn't exist. Maybe I will have
> to create it...
> 2013/1/3, Jean-Marc Spaggiari <[EMAIL PROTECTED]>:
>> Done. You can take a look at what I pushed.
>> Regarding locateRegion(final byte regionName) I don't know if there
>> is a faster way to get the first row and the table name from the
>> regionName. Region name should already contain those 2 information. So
>> it should be possible to retrieve that from it instead of getting all
>> the regions and doing the comparison. Any idea if there is any util
>> class to extract the table and the key from the name?
>> 2013/1/3, Jean-Marc Spaggiari <[EMAIL PROTECTED]>:
>>> I will take a look at all of that and keep you posted shortly.
>>> 2013/1/3, Nicolas Liochon <[EMAIL PROTECTED]>:
>>>> Yep, I'm ok with that. It will need to be put in the interface (vs. the
>>>> implementation class). Would be nice if you could implement the two
>>>> methods (i.e. public HRegionLocation locateRegion(final byte 
>>>> On Thu, Jan 3, 2013 at 7:33 PM, Jean-Marc Spaggiari
>>>> <[EMAIL PROTECTED]
>>>>> public List<HRegionLocation> locateRegions(byte tableName, final