As null insertion causes tombstone in cassandra and null is used most often in relation db like mysql how can one migrate data from mysql to cassandra and avoid tombstone. Is there need to perform compaction manually after migration to remove tombstone please suggest what should be done in this case i am confused with the same
How do we avoid tombstones when migrating relational DB data to Cassandra?
@adampaul, to better answer you question, could you update your original question with details of the Apache Cassandra (C*) or DataStax Enterprise version plus the drivers/connector versions (preferably in groupId:artifactId:version format)?
@adampaul, to better answer you question, could you update your original question with details of the Apache Cassandra (C*) or DataStax Enterprise or DataStax Astra version plus the drivers/connector versions (preferably in groupId:artifactId:version format)? For example, if you're using Spark Cassandra Connector and a version of C* that supports unset, you could leverage properties to ignore saving nulls into the C* table to avoid tombstones getting written into the table in first place. You could also review earlier answers on this community about tombstones and how do they cleaned up.
8 People are following this question.
