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

Sub-range selection for non-frozen collections should return null instead of empty

Agile BoardAttach 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
    • None
    • None
    • None
    • Low

    Description

      For non frozen collections, Cassandra cannot differentiate an empty collection from a null one. Due to that Cassandra returns always null for non-frozen empty collection.

      When selecting a sub range from a non-frozen collection, if the range does not contains any data an empty collection will be returned. It is counter intuitive and a null value should be returned instead.

      CREATE TABLE IF NOT EXISTS t (k int PRIMARY KEY, v set<int>);
      
      INSERT INTO t (k, v) VALUES (1, {});
      SELECT v FROM t; -- null
      SELECT v[1] FROM t; -- null
      SELECT v[1..] FROM t; -- null
      
      INSERT INTO t (k, v) VALUES (1, {0});
      SELECT v FROM t; -- {0}
      SELECT v[1] FROM t; -- null
      SELECT v[1..] FROM t; -- {}
      

      Attachments

        Activity

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

          People

            blerer Benjamin Lerer Assign to me
            blerer Benjamin Lerer
            Benjamin Lerer
            Andres de la Peña
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Slack

                Issue deployment