cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Joshua Galbraith (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-11424) Option to leave omitted columns in INSERT JSON unset
Date Wed, 27 Jul 2016 00:15:20 GMT


Joshua Galbraith commented on CASSANDRA-11424:

We just ran into this issue recently with 2.2.6. Is there any chance this option could make
it into a future 2.2.x release?

> Option to leave omitted columns in INSERT JSON unset
> ----------------------------------------------------
>                 Key: CASSANDRA-11424
>                 URL:
>             Project: Cassandra
>          Issue Type: Improvement
>            Reporter: Ralf Steppacher
>            Assignee: Oded Peer
>              Labels: client-impacting, cql
>             Fix For: 3.10
>         Attachments: 11424-trunk-V1.txt, 11424-trunk-V2.txt, 11424-trunk-V3.txt
> CASSANDRA-7304 introduced the ability to distinguish between {{NULL}} and {{UNSET}} prepared
statement parameters.
> When inserting JSON objects it is not possible to profit from this as a prepared statement
only has one parameter that is bound to the JSON object as a whole. There is no way to control
{{NULL}} vs {{UNSET}} behavior for columns omitted from the JSON object.
> Please extend on CASSANDRA-7304 to include JSON support.
> {color:grey}
> (My personal requirement is to be able to insert JSON objects with optional fields without
incurring the overhead of creating a tombstone of every column not covered by the JSON object
upon initial(!) insert.)
> {color}

This message was sent by Atlassian JIRA

View raw message