> Jean-Daniel Cryans commented on HBASE-546: > ------------------------------------------ > > In Bigtable paper, page 4, it describes what Chubby is used > for exactly : > > - Ensure there is at most 1 active master at any time > - Store the bootstrap location > - Discover tablet servers and finalize tabler server death > - Store the schema information > - Store access control lists (not sure what it is) > > Ze big question : do we want to implement all of these or > just some parts? For example, what would be the benefit of > storing all schema information in ZK instead of what we do right now?
Currently the schema is stored in every row of the meta. Multiple copies = wasted space. Also, it would make schema changes/queries easier: - does a table exist? - create/delete, enable/disable table - add/remove/modify column See HBASE-451 No virus found in this outgoing message. Checked by AVG. Version: 8.0.100 / Virus Database: 270.2.0/1497 - Release Date: 6/11/2008 8:32 AM
