-
Notifications
You must be signed in to change notification settings - Fork 18
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
writetime and TTL are not preserved if columns are not explicitly configured in cdm.properties #218
Comments
icaredb
added a commit
to icaredb/cassandra-data-migrator
that referenced
this issue
Nov 15, 2023
Suggested fix for the following issue: datastax#218 writetime and TTL are not preserved if columns are not explicitly configured in cdm.properties
3 tasks
icaredb
added a commit
to icaredb/cassandra-data-migrator
that referenced
this issue
Nov 15, 2023
Fix for Jira datastax#218 writetime and TTL are not preserved if columns are not explicitly configured in cdm.properties
msmygit
pushed a commit
to icaredb/cassandra-data-migrator
that referenced
this issue
Nov 15, 2023
Suggested fix for the following issue: datastax#218 writetime and TTL are not preserved if columns are not explicitly configured in cdm.properties
msmygit
pushed a commit
to icaredb/cassandra-data-migrator
that referenced
this issue
Nov 15, 2023
Fix for Jira datastax#218 writetime and TTL are not preserved if columns are not explicitly configured in cdm.properties
3 tasks
Implemented as part of #226 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
With the following settings in
cdm.properties
, the writetime and TTL values are not preserved when data is migrated to target cluster. Notespark.cdm.schema.origin.column.ttl.names
andspark.cdm.schema.origin.column.writetime.names
are not explicitly set.Although the automatic TTLCols and WriteTimestampCols are detected correctly, logging shows feature writetimeTTL is disabled:
Reproducing steps:
cdm.properties
contents set as below:The text was updated successfully, but these errors were encountered: