This solution is very "sql-like", meaning that you query what you want when
you need it.
Unfortunately this will probably not scale as your data grows, you might
want to consider de-normalizing your data. You could maintain a min/max
average in the application that inserts the data, or have a batch
Great, so is there any reason I wouldn't want to set gc_grace_seconds to 0
on an "insert once/ttl only" column family, since it feels like the best
thing to do?
On Fri, Jun 5, 2015 at 5:35 PM, Tyler Hobbs wrote:
>
> On Fri, Jun 5, 2015 at 10:30 AM, Kévin LOVATO wrote:
&g
Hi,
I have a column family with data (metrics) that is never overwritten and
only deleted using TTLs, and I am wondering if it would be reasonable to
have a very low gc_grace_period (even 0) on that CF. I would like to do
that mainly to save space and also to prevent tombstone scanning.
>From wha
Hi,
We experienced a crash on our production cluster following a massive wide
row read.
A client tried to read a wide row (~4GB of raw data) without specifying any
slice condition, which resulted in the crash of multiple nodes (as many as
the replication factor) after long garbage collections.
We
