Uploaded image for project: 'Cassandra'
  1. Cassandra
  2. CASSANDRA-11424

Option to leave omitted columns in INSERT JSON unset

Agile BoardAttach filesAttach ScreenshotBulk Copy AttachmentsBulk Move AttachmentsVotersWatch issueWatchersCreate sub-taskConvert to sub-taskMoveLinkCloneLabelsUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

Details

    • Improvement
    • Status: Resolved
    • Normal
    • Resolution: Fixed
    • 3.10
    • None
    • Clients

    Description

      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.


      (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.)

      Attachments

        1. 11424-trunk-V1.txt
          6 kB
          Oded Peer
        2. 11424-trunk-V2.txt
          11 kB
          Oded Peer
        3. 11424-trunk-V3.txt
          13 kB
          Oded Peer

        Activity

          This comment will be Viewable by All Users Viewable by All Users
          Cancel

          People

            odpeer Oded Peer Assign to me
            ralfsteppacher Ralf Steppacher
            Oded Peer
            Sylvain Lebresne
            Votes:
            0 Vote for this issue
            Watchers:
            10 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Slack

                Issue deployment