What you're wanting really isn't supported/available, but you could
probably extend cassandra to do this with some work.
Doing this at replication time is the wrong point, though - you want to do
it before the mutation is applied locally, so triggers are still the
closest to the right point as
Looks like you’ve got this thread going on the user & dev ML. This list is the
dev one, and is meant for discussion of the Cassandra project. Would everyone
mind replying to the thread of the same name on the user list instead?
> On Nov 16, 2017, at 1:36 PM, Abdelkrim Fitouri
ok please find bellow an example:
Lets suppose that i have a cassandra cluster of 4 nodes / one DC /
replication factor = 4, So in this architecture i have on full copy of the
data on each node.
Imagine now that one node have been hacked and in some way with full access
to cqlsh session, if data
g/doc/latest/cql/security.html
Regards,
--
Jacques-Henri Berthemet
-Original Message-
From: Abdelkrim Fitouri [mailto:abdou@gmail.com]
Sent: jeudi 16 novembre 2017 18:31
To: dev@cassandra.apache.org
Subject: custom validation before replication
Hi,
I have some security constraint on a pro
Going to hate myself for this, but check out the trigger interface.
https://github.com/apache/cassandra/blob/cassandra-3.0/src/java/org/apache/cassandra/triggers/ITrigger.java
Pay attention to the note that says the API is in beta and subject to
change. It's had that note for many years, which
16 novembre 2017 18:31
To: dev@cassandra.apache.org
Subject: custom validation before replication
Hi,
I have some security constraint on a project, and i need to validate or
unvalidate changes made on a keyspace via cql or via an other ways before
replication.
for example in the case
Hi,
I have some security constraint on a project, and i need to validate or
unvalidate changes made on a keyspace via cql or via an other ways before
replication.
for example in the case of multinode cluster with replication, if data was
changed locally using cqlsh, data will be replicated (that
