not completely deleted when TTL expires, then the behavior
>>> is definitely fishy, and should probably be filed as a bug.
>>>
>>>
>>>
>>> To your other question, once a TTL update is expired, you can't infer
>>> its past existence through
red, you can't infer its
>> past existence through any queries.
>>
>>
>>
>> Daniel
>>
>>
>>
>> *From:* J Robert Ray [mailto:jrobert...@gmail.com]
>> *Sent:* Monday, February 24, 2014 11:10 PM
>> *To:* user@cassandra.apache.org
&g
n't infer its
> past existence through any queries.
>
>
>
> Daniel
>
>
>
> *From:* J Robert Ray [mailto:jrobert...@gmail.com]
> *Sent:* Monday, February 24, 2014 11:10 PM
> *To:* user@cassandra.apache.org
> *Subject:* Mixing CAS and TTL.
>
>
>
> H
stion, once a TTL update is expired, you can't infer its
past existence through any queries.
Daniel
From: J Robert Ray [mailto:jrobert...@gmail.com]
Sent: Monday, February 24, 2014 11:10 PM
To: user@cassandra.apache.org
Subject: Mixing CAS and TTL.
Hi, I am trying to mix CAS and TTL
Hi, I am trying to mix CAS and TTL and am wondering if this behavior that I
am seeing is expected.
I'm on 2.0.2 and using the java datastax 2.0.0-rc3 client.
In my application, a server "claims" a row by assigning a value to a row
using CAS, expecting the column to start out null. The column has
