cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sam Tunnicliffe (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (CASSANDRA-9421) TriggerExecutor should not wrap all execution exceptions in a RuntimeException
Date Fri, 18 Mar 2016 12:00:37 GMT

     [ https://issues.apache.org/jira/browse/CASSANDRA-9421?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Sam Tunnicliffe updated CASSANDRA-9421:
---------------------------------------
       Resolution: Fixed
    Fix Version/s:     (was: 2.2.x)
                   3.6
           Status: Resolved  (was: Patch Available)

Thanks, committed to trunk in {{6f067af5157be9ed8df566d0a5df042c694215e2}}

> 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
>            Assignee: Branimir Lambov
>            Priority: Minor
>              Labels: lhf
>             Fix For: 3.6
>
>
> 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)

Mime
View raw message