How about multiple tables with 2 column families per table ? On Mon, Jul 18, 2011 at 8:37 PM, Sheng Chen <[email protected]> wrote:
> Sorry, I'm not sure whether I've made myself clear. > > My question is, if HBase currently does not do well with anything about two > or three column families, as said in the HBase book, when I really need > many > column families, is it better to divide them into separate tables, each of > which has only one column family? > > Thanks for any advice. > > > > 2011/7/18 Sheng Chen <[email protected]> > > > I have a few (about 10) groups of columns with similar keys. Each group > has > > a different access pattern. For most keys, there is only one group that > has > > a value. > > Since 'HBase currently does not do well with anything about two or three > > column families', does it mean that it is a better idea to use different > > tables instead of different column families? > > > > Thanks. > > > > Sheng > > >
