-
Notifications
You must be signed in to change notification settings - Fork 22
CASSANALYTICS-32 expose number of rows which violated constraints to JobStats #120
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
base: trunk
Are you sure you want to change the base?
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -45,6 +45,7 @@ public enum WriterOptions implements WriterOption | |
| COMMIT_THREADS_PER_INSTANCE, | ||
| COMMIT_BATCH_SIZE, | ||
| SKIP_EXTENDED_VERIFY, | ||
| SKIP_ROWS_VIOLATING_CONSTRAINTS, | ||
|
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Can you maybe add a comment here that this feature is only available in Cassandra 5.0 version? Or is it 6?
Contributor
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. @frankgh thank you for the review but I am not sure this approach is still viable based on the discussion in the related ticket. Did I interpret that comment correctly when I think that what I did here is itself not enough to consider CASSANALYTICS-32 to be resolved as we need to expose failed rows somehow, but this I am trying to do here is nice to have / the first step towards that direction which is valuable already to have as such?
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Yeah, I saw the comment from Yifan after I reviewed the PR. I think it's a good first approach, you need to explicitly enable this feature in order to write data that does not violate the constraints. |
||
| WRITE_MODE, | ||
| KEYSTORE_PASSWORD, | ||
| KEYSTORE_PATH, | ||
|
|
||
Uh oh!
There was an error while loading. Please reload this page.