This repository has been archived by the owner on Aug 19, 2024. It is now read-only.
Add support for document deletion, operation type and log level setup… #20
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
… to log the record stream
|
can we merge this pull request in? any reason not to merge in? |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
This add following features
Add OperationType in Keys attribute map. This help the Kafka consumer determine the Dynamodb operation type like - INSERT, MODIFY, REMOVE.
Handle the deletion of data. In this case, the code doesn't attempt to get the new image, instead adds Keys with OperationType="REMOVE"
Add a logging flag in the properties file called log.record.stream. If this is true, code spits out the exact record retrieved from DynamoDB. This is useful in case of debugging but also if someone wants to monitor the data using ELK or Splunk.