Hi Rob, thanks for the refresher, and the the issue link (fixed today too- thanks Sylvain!).
Cheers, Lee On Wed, Dec 18, 2013 at 10:47 AM, Robert Coli <rc...@eventbrite.com> wrote: > On Wed, Dec 18, 2013 at 9:26 AM, Lee Mighdoll <l...@underneath.ca> wrote: > >> What's the current cassandra 2.0 advice on sizing for wide storage engine >> rows? Can we drop the added complexity of managing day/hour partitioning >> for time series stores? >> > > "A few hundred megs" at very most is generally > recommended. in_memory_compaction_limit_in_mb still defaults to 64mb, so > rows greater than this size are compacted on disk... > > Cassandra 2.0 and CQL3 storage don't meaningfully change underlying > storage assumptions. It just packs an abstraction layer on top. Cassandra > 2.1 moves some of that abstraction down into storage, but most fundamental > assumptions will still remain the same. > > https://issues.apache.org/jira/browse/CASSANDRA-5417 > > =Rob >
