Bringing together the Apache Cassandra experts from the community and DataStax.

Want to learn? Have a question? Want to share your expertise? You are in the right place!

Not sure where to begin? Getting Started

 

question

adampaul avatar image
adampaul asked ·

How do we avoid tombstones when migrating relational DB data to Cassandra?

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

dsesparktombstonesmigration
1 comment
10 |1000 characters needed characters left characters exceeded

Up to 8 attachments (including images) can be used with a maximum of 1.0 MiB each and 10.0 MiB total.

@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)?

0 Likes 0 · ·

1 Answer

smadhavan avatar image
smadhavan answered ·

@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.

Share
10 |1000 characters needed characters left characters exceeded

Up to 8 attachments (including images) can be used with a maximum of 1.0 MiB each and 10.0 MiB total.