[
https://issues.apache.org/jira/browse/CASSANDRA-7472?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14049145#comment-14049145
]
Tyler Hobbs commented on CASSANDRA-7472:
----------------------------------------
+1 on the patch, but it would be nice to have some test coverage. Perhaps you
could use the new [python driver dtest
branch|https://github.com/riptano/cassandra-dtest/tree/python-driver]? (I
think it's going to be merged into the master branch soon.)
> Prepared marker for collections inside UDT are not properly handled
> -------------------------------------------------------------------
>
> Key: CASSANDRA-7472
> URL: https://issues.apache.org/jira/browse/CASSANDRA-7472
> Project: Cassandra
> Issue Type: Bug
> Reporter: Sylvain Lebresne
> Assignee: Sylvain Lebresne
> Fix For: 2.1.0
>
> Attachments: 7472.txt
>
>
> Collections inside UDT needs to be encoded with the v3 protocol. However, we
> allow to prepare queries like:
> {noformat}
> INSERT INTO foo (k, v) VALUES (0, { s: ? });
> {noformat}
> In that case, if {{s}} is a collection, a client driver will only know that a
> collection is expected for that prepared variable, but it will have no way to
> know for sure that this collection is really part of a UDTValue. So we should
> handle this server side (i.e. let the user send the collection encoded with
> the protocol v2, but re-encode it properly).
--
This message was sent by Atlassian JIRA
(v6.2#6252)
