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.

Sign up for GitHub

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

Jump to bottom

Consistency levels are always LOCAL_ONE #257

Open
hungfaileung opened this issue Apr 4, 2024 · 0 comments · May be fixed by #258
Open

Consistency levels are always LOCAL_ONE #257

hungfaileung opened this issue Apr 4, 2024 · 0 comments · May be fixed by #258

Comments

@hungfaileung
Copy link

Read/write operations are using LOCAL_ONE as consistency level.

Set spark.cdm.perfops.consistency.read or spark.cdm.perfops.consistency.write is not helpful.

Seems that the consistency levels are set at bound statements. Batch statement does not set consistency level and it is null.
So it is using LOCAL_ONE as default value.

When using batch statement, seems that the options set for each statement are ignored.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Fixes issue-257: Sets write consistency on Batch statement arvy/cassandra-data-migrator
1 participant
@hungfaileung