Triggers are identified by a name defined by:
Creating a new trigger uses the
CREATE TRIGGER statement:
create_trigger_statement ::= CREATE TRIGGER [ IF NOT EXISTS ]
CREATE TRIGGER myTrigger ON myTable USING 'org.apache.cassandra.triggers.InvertedIndex';
The actual logic that makes up the trigger can be written in any Java (JVM) language and exists outside the database.
You place the trigger code in a
lib/triggers subdirectory of the Cassandra installation directory, it loads during
cluster startup, and exists on every node that participates in a cluster. The trigger defined on a table fires before a
requested DML statement occurs, which ensures the atomicity of the transaction.