[CASSANDRA-9334] Returning null from a trigger does not abort the write

• Type: Bug
• Status: Resolved
• Priority: Normal
• Resolution: Fixed
• Fix Version/s: 2.0.16, 2.1.6, 2.2.0 beta 1
• Component/s: Legacy/Coordination
• Severity: Normal
• Assignee: Sam Tunnicliffe
• Reporter: Brandon Williams

Authors

Sam Tunnicliffe

Reviewers

Brandon Williams

• Created: 08/May/15 14:49
• Updated: 16/Apr/19 09:31
• Resolved: 19/May/15 11:14

Description

The javadoc for ITrigger seems to indicate that returning null means no mutations for the write will be applied at all:

     * Called exactly once per CF update, returned mutations are atomically updated.
     *
     * @param key - Row Key for the update.
     * @param update - Update received for the CF
     * @return modifications to be applied, null if no action to be performed.

and indeed, TriggerExecutor.execute seems to have code for this:

        if (augmentedMutations == null)
            return null;

but it never fires. In testing with a trigger that always returns null, the original mutation is still applied.