[
https://issues.apache.org/jira/browse/CASSANDRA-10142?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14709472#comment-14709472
]
Sylvain Lebresne commented on CASSANDRA-10142:
----------------------------------------------
I agree with what's above: we should pretend it's a list if it's not properly
encoded as a list for the version of the protocol in use. If we do decide to go
with CASSANDRA-10146, then it's not a problem for 3.0, but that is still
something to fix in prior versions. And agreed also on the solutions, we can
either:
* send frozen types always as a custom type
* or simply make sure we use 2 bytes for the size
A priori I have a preference for the 2nd option (unless of course there is a
complication I'm not thinking of) since that will provide a better experience
to users (even though in practice users should use protocol v3 if they are
going to use frozen types).
> 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
> Fix For: 2.1.x, 2.2.x
>
> 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)
