Uploaded image for project: 'Spring Data for Apache Cassandra'
  1. Spring Data for Apache Cassandra
  2. DATACASS-420

Literal null values in inserts/updates causing cell tombstones

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Critical
    • Resolution: Fixed
    • Affects Version/s: 1.5.1 (Ingalls SR1)
    • Component/s: Core
    • Labels:
      None

      Description

      This issue is caused by the fix for DATACASS-182. Prior to that, the MappingCassandraConverter did not allow inserting literal null values. Now, it does not allow not setting them. Setting literal null values in Cassandra causes cell tombstones which take up space and are detrimental to performance.

      Ideally, there would be an option (preferably at the query level) to say whether or not to insert literal null values, because in some instances, as described by DATACASS-182 you do want to insert literal nulls. I would suggest that the default behavior should be to not insert literal nulls though, because in my opinion it would be more of an exception to the rule that you actually want to insert a literal null since (in my experience) you are mostly inserting new records and not updating existing ones. The offending code is in writeInsertFromWrapper.

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              mp911de Mark Paluch
              Reporter:
              papaswede Emil Berglind
              Last updater:
              Oliver Drotbohm
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved:
                Days since last comment:
                3 years, 24 weeks, 5 days ago