Cassandra
  1. Cassandra
  2. CASSANDRA-5017

Preparing UPDATE queries with collections returns suboptimal metadata

    Details

    • Type: Bug Bug
    • Status: Resolved
    • Priority: Minor Minor
    • Resolution: Fixed
    • Fix Version/s: 1.2.0 rc1
    • Component/s: None
    • Labels:
      None

      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

          Activity

            People

            • Assignee:
              Sylvain Lebresne
              Reporter:
              Aleksey Yeschenko
              Reviewer:
              Aleksey Yeschenko
            • Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                Development