Re: CQL update and TTL

2013-04-26 Thread Sylvain Lebresne
> is there a way to either make TTL dynamic (using ?) > Not at this time. There is https://issues.apache.org/jira/browse/CASSANDRA-4450 open for that, but that's not done yet. > tell the engine not to cache the Prepared statement. I am using the new > CQL Java Driver. > In that case, just don'

Re: CQL update and TTL

2013-04-26 Thread Shahryar Sedghi
Thanks Sylvain So how to avoid the prepared statement cache exhaustion, is there a way to either make TTL dynamic (using ?) or tell the engine not to cache the Prepared statement. I am using the new CQL Java Driver. Shahryar On Fri, Apr 26, 2013 at 11:42 AM, Sylvain Lebresne wrote: > This is

Re: CQL update and TTL

2013-04-26 Thread Alain RODRIGUEZ
That is more or less what I was guessing, thanks for these precision. 2013/4/26 Sylvain Lebresne > This is indeed intended. That behavior is largely dictated by how the > storage engine works, and the fact that an update does no read internally > in particular. > > Yet, what I do not know is wh

Re: CQL update and TTL

2013-04-26 Thread Sylvain Lebresne
This is indeed intended. That behavior is largely dictated by how the storage engine works, and the fact that an update does no read internally in particular. Yet, what I do not know is whether this behavior can be changed somehow to > let the initial TTL, > There's nothing like that supported, n

Re: CQL update and TTL

2013-04-26 Thread Shahryar Sedghi
The issue is, I can get the original TTL using the select and use it for the update, however since TTL can not be dynamic (using ?) it will exhaust the prepared statement cache, because I have tons of updates like this and every one will have a different signature due to changing TTL. I am using

Re: CQL update and TTL

2013-04-26 Thread Alain RODRIGUEZ
This seems to be the correct behavior. An update refreshes the TTL, as it does in memcache for example. Yet, what I do not know is whether this behavior can be changed somehow to let the initial TTL, this might be useful on some use cases. Alain 2013/4/26 Shahryar Sedghi > Apparently when I up

CQL update and TTL

2013-04-26 Thread Shahryar Sedghi
Apparently when I update a column using CQL that already has a TTL, it resets the TTL to null, so if there was already a TTL for all columns that I inserted part of a composite column set, this specific column that I updated will not expire while the others are are getting expired. Is it how it is