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

Decide how to handle with null multi-cell collections

    XMLWordPrintableJSON

    Details

    • Type: Improvement
    • Status: Resolved
    • Priority: Low
    • Resolution: Duplicate
    • Fix Version/s: None
    • Component/s: None
    • Labels:
      None

      Description

      CASSANDRA-10650 introduced the ability to generate the CQL literal from a serialized representation - currently only used to store a UDA's INITCOND.

      The code to generate the CQL literal for a null collection deals with that in the following way:

      • null frozen collections --> CQL literal null
      • empty frozen collections --> CQL literal [] (or {} for maps)
      • null multi-cell collections --> CQL literal [] (or {} for maps) ; there's no way to distinguish null from empty
      • empty multi-cell collections --> CQL literal [] (or {} for maps) ; there's no way to distinguish null from empty

      CASSANDRA-10840 exposed that the handling is not optimal and the patch deals with this by using a "frozen" state type to generate the CQL literal.

      It's currently not a critical thing yet - just want to know whether it's ok how CASSANDRA-10840 handles this or CQL3Type.toCQLLiteral should be changed.

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                Unassigned
                Reporter:
                snazy Robert Stupp
              • Votes:
                0 Vote for this issue
                Watchers:
                3 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: