[
https://issues.apache.org/jira/browse/CASSANDRA-5017?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13510595#comment-13510595
]
Aleksey Yeschenko commented on CASSANDRA-5017:
----------------------------------------------
Everything works now (prepared and unprepared). +1
> Preparing UPDATE queries with collections returns suboptimal metadata
> ---------------------------------------------------------------------
>
> Key: CASSANDRA-5017
> URL: https://issues.apache.org/jira/browse/CASSANDRA-5017
> Project: Cassandra
> Issue Type: Bug
> Affects Versions: 1.2.0 beta 2
> Reporter: Aleksey Yeschenko
> Assignee: Sylvain Lebresne
> Priority: Minor
> Fix For: 1.2.0 rc1
>
> Attachments: 0001-Return-correct-metadata-when-preparing-map.txt,
> 0002-Fix-prepared-list-index-and-using-integer-for-map-keys.txt,
> 0003-Fix-handling-of-prepared-marker-for-deletes.txt,
> 0004-Update-validation-of-ListOperation.txt
>
>
> CQL3, binary protocol.
> collections (id int primary key, amap map<int, varchar>);
> preparing "UPDATE test.collections SET amap[?] = ? WHERE id = ?" returns the
> following metadata:
> [{column,<<"test">>,<<"collections">>,<<"amap">>,
> {map,int,varchar}},
> {column,<<"test">>,<<"collections">>,<<"amap">>,
> {map,int,varchar}},
> {column,<<"test">>,<<"collections">>,<<"id">>,int}]
> Ideally it should return [int, varchar, int] types. Less ideally [{map, int,
> varchar}, int] and expect an encoded map with a single key-value pair. But
> certainly not what it currently returns.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
