[CASSANDRA-10849] Decide how to handle with null multi-cell collections

• Type: Improvement
• Status: Resolved
• Priority: Low
• Resolution: Duplicate
• Assignee: Unassigned
• Reporter: Robert Stupp
• Created: 12/Dec/15 01:14
• Updated: 16/Apr/19 09:30
• Resolved: 22/Feb/16 09:33

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.

Issue Links

• duplicates: CASSANDRA-11064 Failed aggregate creation breaks server permanently