Uploaded image for project: 'Cassandra'
  1. Cassandra
  2. CASSANDRA-5017

Preparing UPDATE queries with collections returns suboptimal metadata

Log workAgile BoardRank to TopRank to BottomAttach filesAttach ScreenshotBulk Copy AttachmentsBulk Move AttachmentsVotersWatch issueWatchersCreate sub-taskConvert to sub-taskMoveLinkCloneLabelsUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

Details

    • Bug
    • Status: Resolved
    • Low
    • Resolution: Fixed
    • 1.2.0 rc1
    • None
    • None
    • Low

    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.

      Attachments

        Issue Links

        Activity

          This comment will be Viewable by All Users Viewable by All Users
          Cancel

          People

            slebresne Sylvain Lebresne Assign to me
            aleksey Aleksey Yeschenko
            Sylvain Lebresne
            Aleksey Yeschenko
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Slack

                Issue deployment