Add commit_time from record to Kafka instead of response safe_time #242
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
vaibhav-yb
approved these changes
Jul 6, 2023
vaibhav-yb
requested changes
Jul 6, 2023
src/main/java/io/debezium/connector/yugabytedb/YugabyteDBStreamingChangeEventSource.java
Outdated
Show resolved
Hide resolved
vaibhav-yb
approved these changes
Jul 8, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
While we are pushing records to Kafka, we will consider the commit_time of each record, instead of the response safe_time.
This also ensure that when we get a Kafka callback acknowledging the record is pushed and persisted in Kafka, we will resuse the same commit_time while setting the checkpoint in cdc_service.