[
https://issues.apache.org/jira/browse/HBASE-451?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13051197#comment-13051197
]
Subbu M Iyer commented on HBASE-451:
------------------------------------
Stack:
Checked your patch and this is exactly what I was trying to fight with.
Hopefully it works this time. A simple test would be to run the
TestColumnPrefixFilter and see if it succeeds. It used to hang around the PUT
and it is a positive sign if this one succeeds.
Let me know your findings. My MVN version is 3.0.2 and as I mentioned my
problem occurs only with newer version of pom.
> 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-Fixed_broken_TestAdmin.patch,
> HBASE-451-Fixed_broken_TestAdmin1.patch,
> 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,
> pass_htd_on_region_construction.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
