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?
Has anyone worked with graalvm to include a cql driver in the native-image
build?
Looking to see if it is possible or known to not be possible?
Thanks,
Chris
Let's say I have a 3 node cluster on 3.11.4 on which authentication is
enabled but authorization is disabled. It has one non-super login user
'user1' and default super user 'cassandra'
In cassandra.yaml
authenticator: PasswordAuthenticator
authorizer: AllowAllAuthorizer
So to enable authorization
Hi,
before changing the configuration from `AllowAllAuthorizer` to
`CassandraAuthorizer`, you need to grant enough permissions to the user
that allow all the accessed tables by that user. I think that should fix
the problem.
Thanks
On Thu, May 9, 2019 at 12:02 PM Laxmikant Upadhyay
wrote:
> Le
