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

Use "replace" in all write modes #43

Merged
merged 2 commits into from
Dec 29, 2022
Merged

Conversation

akudiyar
Copy link
Collaborator

  • Update cartridge-java to v0.10.0, including bugfix for batch operation errors parsing
  • Use replace operation for all DataSet write modes

Fixes #42

@akudiyar akudiyar changed the title Replace in write operations Use "replace" in all write modes Dec 29, 2022
@akudiyar akudiyar force-pushed the replace-in-write-operations branch 2 times, most recently from 2ca7a8e to 7f207f5 Compare December 29, 2022 16:26
Although the insert operations adds additional safety against unexpected
record duplicates, the Spark execution specifics require the write
operations to be idempotent, because in case of a sudden operation
failure it may be retried by Spark automatically, and we cannot delete
existing records prior to it due to the absence of cluster transactions
and extended partitioning support.
@akudiyar akudiyar merged commit 52b1601 into master Dec 29, 2022
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.

Use "replace" operation instead of "insert" for all write modes
1 participant