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

["Oded Peer (JIRA)" <ji...@apache.org>]

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

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

Since new syntax was added for JSON select and insert support I feel comfortable adding new constructs for the new syntax.
Therefore I suggest adding a new keyword to the JSON insert statement adding an optional keyword "IGNORE_OMITTED" which controls the effect of omitted columns. Insert statements with IGNORE_OMITTED will not create tombstones for omitted columns.


> 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: Bug
>            Reporter: Ralf Steppacher
>
> 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)