Ben, to address your question, read my last post but to summarize, yes, there is less overhead in memory to prefix keys than manage multiple Cfs EXCEPT when doing map/reduce. Doing map/reduce, you will now have HUGE overhead in reading a whole slew of rows you don't care about as you can't map/reduce a single virtual CF but must map/reduce the whole CF wasting TONS of resources.
Thanks, Dean On 10/1/12 3:38 PM, "Ben Hood" <0x6e6...@gmail.com> wrote: >On Mon, Oct 1, 2012 at 9:38 PM, Brian O'Neill <b...@alumni.brown.edu> >wrote: >> Its just a convenient way of prefixing: >> >>http://hector-client.github.com/hector/build/html/content/virtual_keyspac >>es.html > >So given that it is possible to use a CF per tenant, should we assume >that there at sufficient scale that there is less overhead to prefix >keys than there is to manage multiple CFs? > >Ben
