i suspect i might be misunderstanding some things. i thought column families were related to packing things together physically. i do not yet have any particular needs in that respect. and hearing about how hbase can only have a few column families i figured i would just stick to 1 for now.
i do have many different datasets. to avoid namespace clashes i figured i would put them in different tables. but now i suspect that approach was wrong and i should use column qualifiers to keep them apart (within one table and one column family). On Thu, Aug 22, 2013 at 12:06 PM, Ted Yu <yuzhih...@gmail.com> wrote: > Roughly how many column families in total do you have ? > > Having many tables would make certain transactions impossible whereas > putting related column families in the same table would allow. > > Cheers > > > On Thu, Aug 22, 2013 at 8:06 AM, Koert Kuipers <ko...@tresata.com> wrote: > > > i read in multiple places that i should try to limit the number of column > > families in hbase. > > > > do i understand it correctly that when i create lots of tables, but they > > all use the same column family (by name), that i am just using one column > > family and i am OK with respect to limiting number of column families ? > > > > thanks! koert > > >
