cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Oded Peer (JIRA)" <>
Subject [jira] [Updated] (CASSANDRA-11424) Add support to "unset" JSON fields in prepared statements
Date Mon, 11 Jul 2016 11:22:11 GMT


Oded Peer updated CASSANDRA-11424:
    Attachment: 11424-trunk-V3.txt

Thank you for the quick feedback.
I see your point. I took the Jira description too literally.
I've fixed it and uploaded patch V3.

> Add support to "unset" JSON fields in prepared statements
> ---------------------------------------------------------
>                 Key: CASSANDRA-11424
>                 URL:
>             Project: Cassandra
>          Issue Type: Improvement
>            Reporter: Ralf Steppacher
>            Assignee: Oded Peer
>              Labels: client-impacting, cql
>             Fix For: 3.8
>         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