accumulo-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Adam Fuchs <>
Subject Re: Accumulo design questions
Date Tue, 06 Nov 2012 21:41:15 GMT
>     4. In supporting dynamic column families, was there a design trade-off
> with
>     respect to the original BigTable or current HBase design?  What might
> be a
>     benefit of doing it the other way?
> One trade-off is that pinning locality groups in memory (i.e. making them
ephemeral) would be challenging for Accumulo, while this is something that
Bigtable supports.

Another trade-off is that supporting compactions on only one locality group
at a time would be impossible. Since any one file can hold all locality
groups, it is likely that all data will go through the compaction channels
even if only one locality group is being actively written. The flip side of
this is that Accumulo uses fewer files, putting less load on HDFS.


View raw message