[
https://issues.apache.org/jira/browse/HBASE-451?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13049487#comment-13049487
]
Subbu M Iyer commented on HBASE-451:
------------------------------------
Stack: Is it really working with out HTD in createHRegion?
We are creating the .tableInfo as part of createHRegion call and we won't be
able to create a .tableInfo if HTD is not passed. Also with out .tableInfo &
HTD during createHRegion most of the tests will fail.
I understand it's kinda wonky to create a .tableInfo for every region creation,
and my original idea was just to do it once at the time of create table. But
there are lot of tests that just create a region (bypassing the create table
and thus no HTD or tableinfo) and to support those cases I had to add this
wonky support.
Let me know how it looks with ur latest patch.
> 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_-_Fourth_draft_support_for_removing_HTD_from_HRI.patch,
> HBASE-451_-_Second_draft_-_Remove_HTD_from_HRI.patch, fixtestadmin.txt
>
>
> 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
