You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Oded Peer (JIRA)" <ji...@apache.org> on 2016/05/10 11:39:13 UTC

[jira] [Commented] (CASSANDRA-11424) Add support to "unset" JSON fields in prepared statements

    [ https://issues.apache.org/jira/browse/CASSANDRA-11424?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15277970#comment-15277970 ] 

Oded Peer commented on CASSANDRA-11424:
---------------------------------------

[~thobbs] What do you think of my previous proposal? {noformat}INSERT INTO ks.tab JSON IGNORE_OMITTED '{"k" : "v"}'{noformat}

> Add support to "unset" JSON fields in prepared statements
> ---------------------------------------------------------
>
>                 Key: CASSANDRA-11424
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-11424
>             Project: Cassandra
>          Issue Type: Improvement
>            Reporter: Ralf Steppacher
>            Assignee: Tyler Hobbs
>
> 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
(v6.3.4#6332)