[
https://issues.apache.org/jira/browse/CASSANDRA-8528?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14485904#comment-14485904
]
Tyler Hobbs commented on CASSANDRA-8528:
----------------------------------------
Somewhat, yes. CASSANDRA-9037 was similar.
Unfortunately there's not much we can do without splitting out that part of the
driver into a separate lib that we can update ourselves.
As a workaround until we're able to resolve that or upgrade the bundled driver,
your function could take no arguments (and return null, if needed).
> 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, 8528-002.txt, 8528-003.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)
