[
https://issues.apache.org/jira/browse/CASSANDRA-11424?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15395158#comment-15395158
]
Sylvain Lebresne commented on CASSANDRA-11424:
----------------------------------------------
We're only committing bug fix to 2.2 at this point, and that's a minor
improvement (anything JSON related is minor in the sense that you can always
work-around any problem/limitation by not using the JSON syntax, which is
merely a convenience), so no, we won't backport it, sorry.
> Option to leave omitted columns in INSERT JSON unset
> ----------------------------------------------------
>
> Key: CASSANDRA-11424
> URL: https://issues.apache.org/jira/browse/CASSANDRA-11424
> 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
(v6.3.4#6332)
