You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@phoenix.apache.org by "Andrew Purtell (JIRA)" <ji...@apache.org> on 2015/02/05 17:41:35 UTC

[jira] [Commented] (PHOENIX-1636) Substitute HRegionInfo for HRegion where possible

    [ https://issues.apache.org/jira/browse/PHOENIX-1636?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14307522#comment-14307522 ] 

Andrew Purtell commented on PHOENIX-1636:
-----------------------------------------

When HBASE-12973 is committed do we bump the minimum supported version of HBase up to the releases that contain them? Or handle it by reflection? The latter option seems an unnecessary perf hit. I suggest the former. 

> Substitute HRegionInfo for HRegion where possible
> -------------------------------------------------
>
>                 Key: PHOENIX-1636
>                 URL: https://issues.apache.org/jira/browse/PHOENIX-1636
>             Project: Phoenix
>          Issue Type: Sub-task
>            Reporter: Andrew Purtell
>
> Some direct use of HRegion can be replaced by passing around and using HRegionInfo instead, we are looking at key ranges or region metadata (region name) or table metadata (HTD, HCD) only.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)