Thanks all for your answer.
Thanks Jeff for clarification. Only thing I could not get is how CAS(I
assume you r talking about compare and set) will help track the offset
consumed within partition. But I got an good idea what you r trying to
explain. Capping partition size and deleting by partition
Using cassandra as a queue is possible if you really really understand the data
model, but most people will do it wrong the first few times
Cap your partition size. The times I’ve seen this done were near 10mb
partitions and used a special hook into internals to track partition size via
any inputs here?
On Sat, May 2, 2020 at 12:49 PM Jai Bheemsen Rao Dhanwada <
jaibheem...@gmail.com> wrote:
> Hello Alain,
>
> Thanks for your suggestions.
>
> Surprisingly, the node which is in unreachable state, is not present in
> any of the system tables. I am wondering, where the information
Hi,
On Sat, May 23, 2020 at 6:26 PM Laxmikant Upadhyay
wrote:
> Thanks you so much for quick response. I completely agree with Jeff and
> Gabor that it is an anti-pattern to build queue in Cassandra. But plan is
> to reuse the existing Cassandra infrastructure without any additional cost
>
Thanks you so much for quick response. I completely agree with Jeff and
Gabor that it is an anti-pattern to build queue in Cassandra. But plan is
to reuse the existing Cassandra infrastructure without any additional cost
(like kafka).
So even if the data is partioned properly (max 10mb per date )
Hi,
On Sat, May 23, 2020 at 4:09 PM Laxmikant Upadhyay
wrote:
> I think that we should avoid tombstones specially row-level so should go
> with option-1. Kindly suggest on above or any other better approach ?
>
Why don't you use a queue implementation, like AcitiveMQ, Kafka and
something?
You’re building a queue
Just use Kafka.
> On May 23, 2020, at 7:09 AM, Laxmikant Upadhyay
> wrote:
>
>
> Hi All,
> I have a query regarding Cassandra data modelling: I have created two tables:
>
> 1. CREATE TABLE ks.records_by_id ( id uuid PRIMARY KEY, status text, details
> text);
>
Laxmikant,
You mentioned that you need to filter records based on status='pending' in
option-1. I don't see that filtering is done in that option. You are setting
status as 'processed' when partition key is matched for table. For delete
(option-2) it will completely remove whole partition for
Hi All,
I have a query regarding Cassandra data modelling: I have created two
tables:
1. CREATE TABLE ks.records_by_id ( id uuid PRIMARY KEY, status text,
details text);
2. CREATE TABLE ks.records_by_date ( date date, id uuid, status text,
PRIMARY KEY(date, id));
I need to fetch records by
