05-19-2017 10:50 AM
I've read the general advice to avoid more than 2-3 column families on an HBase table because of the way flushing works.
I've also come across a HBase ticket that does flushing per family so if a family doesn't have enough data it doesn't cause extra I/O.
Looks like that patch got applied in HBase v1.1 and we're using HBase v1.2. With this flusing change, are there still problems with more than 2-3 families?