I think the recommendation once upon a time was to keep wide storage engine
internal rows from growing too large. e.g. for time series, it was
recommended to partition samples by day or by hour to keep the size
manageable.
What's the current cassandra 2.0 advice on sizing for wide storage engine
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
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
