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

Subbu M Iyer commented on HBASE-451:
------------------------------------

Added second version of patch.

Major changes include:
1. Moved old school HRI to migration package and renamed it to HRegionInfo090x.
2. Creating new .tableInfo in HDFS now follows the two step approach like 
.regionInfo. First create the file under .tmp and then rename it on successful 
create.
3. Addressed most of the review call outs.

> Remove HTableDescriptor from HRegionInfo
> ----------------------------------------
>
>                 Key: HBASE-451
>                 URL: https://issues.apache.org/jira/browse/HBASE-451
>             Project: HBase
>          Issue Type: Improvement
>          Components: master, regionserver
>    Affects Versions: 0.2.0
>            Reporter: Jim Kellerman
>            Assignee: Subbu M Iyer
>            Priority: Critical
>             Fix For: 0.92.0
>
>         Attachments: 451_support_for_removing_HTD_from_HRI_trunk.txt, 
> HBASE-451_-_First_draft_support_for_removing_HTD_from_HRI1.patch, 
> HBASE-451_-_Second_draft_-_Remove_HTD_from_HRI.patch
>
>
> There is an HRegionInfo for every region in HBase. Currently HRegionInfo also 
> contains the HTableDescriptor (the schema). That means we store the schema n 
> times where n is the number of regions in the table.
> Additionally, for every region of the same table that the region server has 
> open, there is a copy of the schema. Thus it is stored in memory once for 
> each open region.
> If HRegionInfo merely contained the table name the HTableDescriptor could be 
> stored in a separate file and easily found.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

Reply via email to