cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Robert Stupp (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-8528) Add an ExecutionException to the protocol
Date Thu, 08 Jan 2015 09:05:34 GMT

    [ https://issues.apache.org/jira/browse/CASSANDRA-8528?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14269014#comment-14269014
] 

Robert Stupp commented on CASSANDRA-8528:
-----------------------------------------

I'd like to transport the function to the client (i.e. its keyspace, name, arg-types) - that's
why I called it FunctionException.

In detail (reported to clients via native protocol):
* new error code for function execution failures, with function + message as payload
* new error code for broken functions, with function + message as payload
* new error code for 'generic' execution exception

Any objections on adding a {{ExecutionException}} and {{FunctionExecutionException}} that
extends EE plus another {{BrokenFunctionException}} ?

> 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
>
>         Attachments: 8528-001.txt
>
>
> 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)

Mime
View raw message