cassandra-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Ali Akhtar <ali.rac...@gmail.com>
Subject Re: Insert Vs Updates - Both create tombstones
Date Wed, 13 May 2015 11:09:50 GMT
Sorry, wrong thread. Disregard the above

On Wed, May 13, 2015 at 4:08 PM, Ali Akhtar <ali.rac200@gmail.com> wrote:

> If specifying 'using' timestamp, the docs say to provide microseconds, but
> where are these microseconds obtained from? I have regular java.util.Date
> objects, I can get the time in milliseconds (i.e the unix timestamp), how
> would I convert that to microseconds?
>
> On Wed, May 13, 2015 at 3:45 PM, Peer, Oded <Oded.Peer@rsa.com> wrote:
>
>>  Under the assumption that when you update the columns you also update
>> the TTL for the columns then a tombstone won’t be created for those columns.
>>
>> Remember that TTL is set on columns (or “cells”), not on rows, so your
>> description of updating a row is slightly misleading. If every query
>> updates different columns then different columns might expire at different
>> times.
>>
>>
>>
>> *From:* Walsh, Stephen [mailto:Stephen.Walsh@Aspect.com]
>> *Sent:* Wednesday, May 13, 2015 1:35 PM
>> *To:* user@cassandra.apache.org
>> *Subject:* Insert Vs Updates - Both create tombstones
>>
>>
>>
>> Quick Question,
>>
>>
>>
>> Our team is under much debate, we are trying to find out if an Update on
>> a row with a TTL will create a tombstone.
>>
>>
>>
>> E.G
>>
>>
>>
>> We have one row with a TTL, if we keep “updating” that row before the TTL
>> is hit, will a tombstone be created.
>>
>> I believe it will, but want to confirm.
>>
>>
>>
>> So if that’s is  true,
>>
>> And if our TTL is 10 seconds and we “update” the row every second, will
>> 10 tombstones be created after 10 seconds? Or just 1?
>>
>> (and does the same apply for “insert”)
>>
>>
>>
>> Regards
>>
>> Stephen Walsh
>>
>>
>>
>>
>>
>> This email (including any attachments) is proprietary to Aspect Software,
>> Inc. and may contain information that is confidential. If you have received
>> this message in error, please do not read, copy or forward this message.
>> Please notify the sender immediately, delete it from your system and
>> destroy any copies. You may not further disclose or distribute this email
>> or its attachments.
>>
>
>

Mime
View raw message