You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@cassandra.apache.org by "Sylvain Lebresne (JIRA)" <ji...@apache.org> on 2014/12/20 14:17:13 UTC

[jira] [Updated] (CASSANDRA-8528) Add an ExecutionException to the protocol

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

Sylvain Lebresne updated CASSANDRA-8528:
----------------------------------------
    Issue Type: Sub-task  (was: Improvement)
        Parent: CASSANDRA-8043

> Add an ExecutionException to the protocol
> -----------------------------------------
>
>                 Key: CASSANDRA-8528
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-8528
>             Project: Cassandra
>          Issue Type: Sub-task
>            Reporter: Sylvain Lebresne
>            Assignee: Robert Stupp
>              Labels: client-impacting, protocolv4
>             Fix For: 3.0
>
>
> With the introduction of UDF, we should add an ExecutionException (or FunctionExecutionException or something like that) to the exceptions that can be sent back to client. We can't guarantee that UDFs won't throw and none of our existing exception is terribly adapted to report such event to the client.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)