You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Sam Tunnicliffe (JIRA)" <ji...@apache.org> on 2015/05/19 13:14:01 UTC
[jira] [Updated] (CASSANDRA-9421) TriggerExecutor should not wrap
all execution exceptions in a RuntimeException
[ https://issues.apache.org/jira/browse/CASSANDRA-9421?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Sam Tunnicliffe updated CASSANDRA-9421:
---------------------------------------
Priority: Minor (was: Major)
Fix Version/s: 2.2.x
Issue Type: Improvement (was: Bug)
> TriggerExecutor should not wrap all execution exceptions in a RuntimeException
> ------------------------------------------------------------------------------
>
> Key: CASSANDRA-9421
> URL: https://issues.apache.org/jira/browse/CASSANDRA-9421
> Project: Cassandra
> Issue Type: Improvement
> Reporter: Sam Tunnicliffe
> Priority: Minor
> Fix For: 2.2.x
>
>
> It may be desirable to have implementations of {{ITrigger#augment}} throw {{RequestValidationException}} or {{RequestExecutionException}} when conditions for applying the trigger are not met (see CASSANDRA-9334 for more discussion). {{TriggerExecutor#executeInternal}} currently catches any exception thrown by a trigger, wraps it in a {{RuntimeException}} and rethrows. It would be better to allow {{CassandraExceptions}} to propagate back to clients directly.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)