cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Robert Stupp (JIRA)" <j...@apache.org>
Subject [jira] [Created] (CASSANDRA-10849) Decide how to handle with null multi-cell collections
Date Sat, 12 Dec 2015 01:15:46 GMT
Robert Stupp created CASSANDRA-10849:
----------------------------------------

             Summary: Decide how to handle with null multi-cell collections
                 Key: CASSANDRA-10849
                 URL: https://issues.apache.org/jira/browse/CASSANDRA-10849
             Project: Cassandra
          Issue Type: Improvement
            Reporter: Robert Stupp
            Priority: Minor


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.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message