[
https://issues.apache.org/jira/browse/HBASE-451?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12607702#action_12607702
]
Jean-Daniel Cryans commented on HBASE-451:
------------------------------------------
IMO, writing the schema in HDFS or in Zookeeper's namespace should be the same
operation so it should not be a major problem, can be the same code but with a
different output. Regarding hbase-fsck, it could read from ZK or from HDFS
depending on the configuration. Last point, ZK is supposed to be "read
optimized" so reading from it when we are using it should be faster than HDFS.
That said, we could just start by putting the schema in HDFS and see if it
causes trouble and then we could consider putting it in ZK.
> Remove HTableDescriptor from HRegionInfo
> ----------------------------------------
>
> Key: HBASE-451
> URL: https://issues.apache.org/jira/browse/HBASE-451
> Project: Hadoop HBase
> Issue Type: Improvement
> Components: master, regionserver
> Affects Versions: 0.2.0
> Reporter: Jim Kellerman
>
> 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.
-
You can reply to this email to add a comment to the issue online.
