[
https://issues.apache.org/jira/browse/CASSANDRA-10142?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14707469#comment-14707469
]
Adam Holmberg commented on CASSANDRA-10142:
-------------------------------------------
I got a chance to look into this a little more. [~thobbs] I'm not sure this is
something the driver should handle. We do not deserialize via FrozenType in
results -- this is a results message coming back with a top-level ListType
mis-encoded for the protocol version in use. I think the server should either
indicate FrozenType in the results metadata (in which case we can use the
strategy you mention), or encode the un-nested collection for the protocol
version in use.
Thoughts?
> Driver cannot connect with protocol version < 3
> -----------------------------------------------
>
> Key: CASSANDRA-10142
> URL: https://issues.apache.org/jira/browse/CASSANDRA-10142
> Project: Cassandra
> Issue Type: Bug
> Reporter: Jim Witschey
> Assignee: Blake Eggleston
> Attachments: repro.sh
>
>
> When trying to connect with the Python driver to a cluster running trunk, the
> connection fails with a {{NoHostAvailable}} exception if the protocol version
> is set to 1 or 2.
> The attached script reproduces the error and demonstrates that the connection
> works if the protocol version is 3 or 4.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
