Anyone?
ср, 8 мая 2019 г. в 11:37, Alexey Knyshev :
> Hi, thanks for your answers!
>
> > Are you asking if writes are atomic at the partition level? If so yes.
> If you have N columns in a simple k/v schema, and you send a write with X/N
> of those columns set, all X will be updated at the same t
Hi, thanks for your answers!
> Are you asking if writes are atomic at the partition level? If so yes. If
you have N columns in a simple k/v schema, and you send a write with X/N of
those columns set, all X will be updated at the same time wherever that
writes goes.
Even for cross dc replication?
Hi, thanks for your answers!
> Are you asking if writes are atomic at the partition level? If so yes. If
you have N columns in a simple k/v schema, and you send a write with X/N of
those columns set, all X will be updated at the same time wherever that
writes goes.
Even for cross dc replication?
Are you asking if writes are atomic at the partition level? If so yes. If
you have N columns in a simple k/v schema, and you send a write with X/N of
those columns set, all X will be updated at the same time wherever that
writes goes.
The CL thing is more about how tolerant you are to stale data,
Depends on the consistency level you are setting on write and read.
What CL are you writing at and what CL are you reading at?
The consistency level tells the coordinator when to send acknowledgement of a
write and whether to cross DCs to confirm a write. It also tells the
coordinator how many
Hi there!
Could someone please explain how Column Family would be replicated and
"visible / readable" in the following scenario? Having multiple
geo-distributed datacenters with significant latency (up to 100ms RTT).
Let's name two of them A and B and consider the following 2 cases:
1. Cassand
