Auth
Sent: Tuesday, November 10, 2020 11:50 AM
To: user@cassandra.apache.org
Subject: [EXTERNAL] Re: Last stored value metadata table
Hi,
On Tue, Nov 10, 2020 at 5:29 PM Durity, Sean R
mailto:sean_r_dur...@homedepot.com>> wrote:
Updates do not create tombstones. Deletes create tomb
Hi,
On Tue, Nov 10, 2020 at 6:29 PM Alex Ott wrote:
> What about using "per partition limit 1" on that table?
>
Oh, it is almost a good solution, but actually the key is ((epoch_day,
name), timestamp), to support more distributed partitioning, so... it is
not good... :/
--
Bye,
Auth Gábor
What about using "per partition limit 1" on that table?
On Tue, Nov 10, 2020 at 8:39 AM Gábor Auth wrote:
> Hi,
>
> Short story: storing time series of measurements (key(name, timestamp),
> value).
>
> The problem: get the list of the last `value` of every `name`.
>
> Is there a Cassandra
Hi,
On Tue, Nov 10, 2020 at 5:29 PM Durity, Sean R
wrote:
> Updates do not create tombstones. Deletes create tombstones. The above
> scenario would not create any tombstones. For a full solution, though, I
> would probably suggest a TTL on the data so that old/unchanged data
> eventually gets
Hi,
On Tue, Nov 10, 2020 at 3:18 PM Durity, Sean R
mailto:sean_r_dur...@homedepot.com>> wrote:
My answer would depend on how many “names” you expect. If it is a relatively
small and constrained list (under a few hundred thousand), I would start with
something like:
At the moment, the number
Hi,
On Tue, Nov 10, 2020 at 3:18 PM Durity, Sean R
wrote:
> My answer would depend on how many “names” you expect. If it is a
> relatively small and constrained list (under a few hundred thousand), I
> would start with something like:
>
At the moment, the number of names is more than 10,000
are, I would look at something time-series
related with a short TTL.)
Sean Durity
From: Gábor Auth
Sent: Tuesday, November 10, 2020 2:39 AM
To: user@cassandra.apache.org
Subject: [EXTERNAL] Last stored value metadata table
Hi,
Short story: storing time series of measurements (key(name
Hi,
Short story: storing time series of measurements (key(name, timestamp),
value).
The problem: get the list of the last `value` of every `name`.
Is there a Cassandra friendly solution to store the last value of every
`name` in a separate metadata table? It will come with a lot of
