Skip to content
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

issue-220: Fixes ttl-writetime auto flag handling #226

Merged
merged 1 commit into from
Dec 12, 2023

Conversation

arvy
Copy link
Contributor

@arvy arvy commented Dec 9, 2023

What this PR does:
Fixes ttl-writetime feature auto flag handling and some tests.

Which issue(s) this PR fixes:
Fixes #220

Checklist:

  • Automated Tests added/updated
  • Documentation added/updated
  • CLA Signed: DataStax CLA

@arvy arvy requested a review from a team as a code owner December 9, 2023 20:42
@@ -101,9 +101,17 @@ spark.cdm.connect.target.password cassandra
# columns need to be listed.
#-----------------------------------------------------------------------------------------------------------
spark.cdm.schema.origin.keyspaceTable keyspace_name.table_name

# Max TTL value of all non-PK columns will be used for insert on target
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

non-PK columns might not be specific enough - not all types support writetime/ttl (collections, counters, etc..). ..so maybe "all ttl-eligible columns" would be a better description..

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Agree. May be "all ttl-eligible non-PK columns" ?

Copy link
Collaborator

@pravinbhat pravinbhat left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good but it will still fail the coverage check due to build issues. Once PR #228 is merged, this should work. You will need to pull changes from main & then merge.

@mfmaher2 mfmaher2 merged commit 9361b79 into datastax:main Dec 12, 2023
0 of 2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants