[CASSANDRA-5017] Preparing UPDATE queries with collections returns suboptimal metadata

• Type: Bug
• Status: Resolved
• Priority: Low
• Resolution: Fixed
• Fix Version/s: 1.2.0 rc1
• Severity: Low
• Assignee: Sylvain Lebresne
• Reporter: Aleksey Yeschenko

Authors

Sylvain Lebresne

Reviewers

Aleksey Yeschenko

• Created: 03/Dec/12 16:35
• Updated: 16/Apr/19 09:32
• Resolved: 10/Dec/12 16:34

Description

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.

Issue Links

• is duplicated by: CASSANDRA-5018 Some queries with collections require quoting the key even when the key is an integer