What if the caching requirements, sorting needs of two kind of data are very much similar, is it preferable to go with a single CF in those cases ?
Regards Aditya >>> On Sat, Feb 5, 2011 at 10:43 AM, Tyler Hobbs<ty...@datastax.com> wrote: >>>>>> >>>>>> I read somewhere that more no of column families is not a good idea as >>>>>> it consumes more memory and more compactions to occur >>>>> >>>>> This is primarily true, but not in every case. >>>>> >>>>>> But the caching requirements may be different as they cater to two >>>>>> different features. >>>>> >>>>> This is a great reason to *not* merge them. Besides the key and row >>>>> caches, >>>>> don't forget about the OS buffer cache. >>>>> >>>>>> Is it recommended to merge these two column families into one ?? >>>>>> Thoughts >>>>>> ? >>>>> >>>>> No, this sounds like an anti-pattern to me. The overhead from having >>>>> two >>>>> separate CFs is not that high. >>>>> >>>>> -- >>>>> Tyler Hobbs >>>>> Software Engineer, DataStax >>>>> Maintainer of the pycassa Cassandra Python client library
