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 it exists now. If you let it apply locally and then try to stop replication, you'll have to also fight: - Commitlog replay - Read repair / consistency levels - Antientropy repair - Hints etc On Thu, Nov 16, 2017 at 1:36 PM, Abdelkrim Fitouri <abdou....@gmail.com> wrote: > 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 is changed on that node, data will be changed on > the three other, am i right ? > > imagine now that i am able to know (using cryptographic bases) if one > column was modified by my API ( => normal way) or not ( => suspicious way), > and i want to execute this check function just before any replication of a > keyspace to avoid that all the replica will be affected by that and so a > rollback will be not easy and the integrity of all the system will be down, > the check will for example kill the local cassandra service ... > > Hope that my question is more clear now. > > Many thanks for any help. > > 2017-11-16 21:59 GMT+01:00 Nate McCall <zznat...@gmail.com>: > > > On Fri, Nov 17, 2017 at 9:11 AM, Abdelkrim Fitouri <abdou....@gmail.com> > > wrote: > > > Trigger does not resolve my problem because it is not a format > validation > > > issue but an integrity constraint ... > > > > > > My purpose is to check data integrity before replication, by returning > an > > > error and killing the service, so i am killing the node that is > supposed > > to > > > replicate data after a write action ... > > > > I'm a little confused. Can you provide some specific examples of your > > requirements? > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: dev-unsubscr...@cassandra.apache.org > > For additional commands, e-mail: dev-h...@cassandra.apache.org > > > > > > > -- > > Cordialement / Best Regards. > > *Abdelkarim FITOURI* > > LPIC/CEH/ITIL > > System And Security Engineer >
