Reputation: 916
How Cassandra supports more number of optimal column families when compared to HBase? Any underlying implementation differences?
Upvotes: 1
Views: 412
Reputation: 19377
HBase currently does not do well with anything above two or three column families so keep the number of column families in your schema low. Currently, flushing and compactions are done on a per Region basis so if one column family is carrying the bulk of the data bringing on flushes, the adjacent families will also be flushed though the amount of data they carry is small.
Cassandra flushes per-columnfamily, per replica. How it determines when to flush each when there are dozens or hundreds of CFs is touched on in this post.
Upvotes: 4