[
https://issues.apache.org/jira/browse/CASSANDRA-8528?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14485881#comment-14485881
]
Adam Holmberg commented on CASSANDRA-8528:
------------------------------------------
When running a client with protocol v4 I'm seeing an error due to a server
dependency on a version of java-driver that does not support v4:
{noformat}
Caused by: java.lang.IllegalArgumentException: No protocol version matching
integer version 4
at
com.datastax.driver.core.ProtocolVersion.fromInt(ProtocolVersion.java:89)
~[cassandra-driver-core-2.1.2.jar:na]
at
org.apache.cassandra.cql3.functions.UDFunction.compose(UDFunction.java:177)
~[main/:na]
{noformat}
(Running C* at 059a56).
Is this known/expected?
> 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)
