;
>
>
> Sean Durity
>
>
>
> *From:* DuyHai Doan
> *Sent:* Monday, September 17, 2018 4:23 PM
> *To:* user
> *Subject:* Re: [EXTERNAL] Re: cold vs hot data
>
>
>
> Sean
>
>
>
> Without transactions à la SQL, how can you guarantee atomicity between
&g
Durity
From: DuyHai Doan
Sent: Monday, September 17, 2018 4:23 PM
To: user
Subject: Re: [EXTERNAL] Re: cold vs hot data
Sean
Without transactions à la SQL, how can you guarantee atomicity between both
tables for upserts ? I mean, one write could succeed with hot table and fail
for cold table
Also for the record, I remember Datastax having something called Tiered
Storage that does move data around (folders/disk volume) based on data age.
To be checked
On Mon, Sep 17, 2018 at 10:23 PM, DuyHai Doan wrote:
> Sean
>
> Without transactions à la SQL, how can you guarantee atomicity between
Sean
Without transactions à la SQL, how can you guarantee atomicity between both
tables for upserts ? I mean, one write could succeed with hot table and
fail for cold table
The only solution I see is using logged batch, with a huge overhead and
perf hit on for the writes
On Mon, Sep 17, 2018 at
An idea:
On initial insert, insert into 2 tables:
Hot with short TTL
Cold/archive with a longer (or no) TTL
Then your hot data is always in the same table, but being expired. And you can
access the archive table only for the more rare circumstances. Then you could
have the HOT table on a differe
