+1 for redis for this use case.
On Aug 16, 2013, at 10:54 AM, Robert Coli wrote:
> On Fri, Aug 16, 2013 at 10:43 AM, Todd Nine wrote:
> We're using expiring columns as a mean for locking.
>
> Perhaps a log structured data store with immutable data files is not ideal
> for your use case?
>
On Fri, Aug 16, 2013 at 10:43 AM, Todd Nine wrote:
> We're using expiring columns as a mean for locking.
Perhaps a log structured data store with immutable data files is not ideal
for your use case?
If I were you, I'd put this use case in Redis and be done with it instead
of trying to get Ca
What about compactions, how often do you run them?
-Original Message-
From: Todd Nine
Sent: Friday, August 16, 2013 1:43 PM
To: user@cassandra.apache.org
Subject: Configuring ephemeral only column family
Hi guys,
We're using expiring columns as a mean for locking. All of this
Hi guys,
We're using expiring columns as a mean for locking. All of this
data should be completely ephemeral with only a 5 second ttl per
column. We're seeing some strangeness where our rows are getting
quite large with tombstones. We really don't need the commit log, nor
the sstables in our u
