You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Matteo Bertozzi (JIRA)" <ji...@apache.org> on 2013/02/07 15:45:19 UTC
[jira] [Updated] (HBASE-7786) Consolidate HRegion creation/opening
API
[ https://issues.apache.org/jira/browse/HBASE-7786?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Matteo Bertozzi updated HBASE-7786:
-----------------------------------
Attachment: HBASE-7786-v0.patch
> Consolidate HRegion creation/opening API
> ----------------------------------------
>
> Key: HBASE-7786
> URL: https://issues.apache.org/jira/browse/HBASE-7786
> Project: HBase
> Issue Type: Bug
> Components: regionserver
> Affects Versions: 0.96.0
> Reporter: Matteo Bertozzi
> Assignee: Matteo Bertozzi
> Attachments: HBASE-7786-v0.patch
>
>
> Currently we have 4 ways to instantiate an HRegion.
> * HRegion.createHRegion()
> * HRegion.openHRegion()
> * HRegion.newHRegion() + r.initialize()
> * new HRegion() + r.initialize()
> Aside from tests and HMerge and SplitTransaction code everyone use createHRegion() and openHRegion(). To avoid errors due to missing initialization calls I think we should limit the access to newHRegion() and the constructor.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira