DynamoDB: Add ctk load table interface for processing CDC events
#247
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
amotl
commented
Aug 29, 2024
Comment on lines
32
to
53
| # TODO: Make configurable. | ||
| create_stream=True, | ||
| iterator_type="TRIM_HORIZON", | ||
| sleep_time_no_records=0.2, |
There was a problem hiding this comment.
Yes. What the comment says.
There was a problem hiding this comment.
iterator_type="TRIM_HORIZON" (currently hard-coded) means it will always read the Stream from its starting point. Sure enough, this is probably the most important detail to be made configurable.
There was a problem hiding this comment.
07b1974 adds a few options to configure details when connecting to the Kinesis Stream.
Comment on lines
52
to
81
| # TODO: Make configurable. | ||
| create_stream=True, | ||
| buffer_time=0.01, |
There was a problem hiding this comment.
07b1974 adds a few options to configure details when connecting to the Kinesis Stream.
amotl
force-pushed
the
amo/dynamodb-cdc-standalone
branch
3 times, most recently
from
092da37 to
c299c4e
Compare
This comment was marked as duplicate.
This comment was marked as duplicate.
Sorry, something went wrong.
wierdvanderhaar
approved these changes
Aug 29, 2024
amotl
force-pushed
the
amo/dynamodb-cdc-standalone
branch
from
c299c4e to
6841aa8
Compare
amotl
commented
Aug 29, 2024
amotl
force-pushed
the
amo/dynamodb-cdc-standalone
branch
from
0ff229f to
9c9cd6b
Compare
amotl
force-pushed
the
amo/dynamodb-cdc-standalone
branch
from
9c9cd6b to
f305462
Compare
In contrast to the Lambda-based processor implementation, this one is a standalone one that can be used optimally in any Python environment, managed or not.
New options: batch-size, create, create-shards, start, seqno, idle-sleep, buffer-time.
amotl
force-pushed
the
amo/dynamodb-cdc-standalone
branch
from
f305462 to
07b1974
Compare
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.
About
Running DynamoDB CDC events through Kinesis and processing them using an AWS Lambda is cumbersome more often than not, and not too suitable for collaboration and development purposes. This patch provides a standalone implementation, as a sister to the corresponding full-load implementation, DynamoDB Table Loader.
Documentation
Preview: https://cratedb-toolkit--247.org.readthedocs.build/io/dynamodb/cdc.html
Synopsis
Use AWS for real, or exercise using LocalStack.
Install
pip install 'cratedb-toolkit[kinesis] @ git+https://github.com/crate/cratedb-toolkit.git@dynamodb-cdc-standalone'Details
This data nozzle is tapping into Change data capture for DynamoDB Streams, in this case using Kinesis Data Streams, for maximum universality, because using Kinesis isn't a bad idea: We will also use it to ingest other event/record types in the future, thus the protocol identifier
kinesis+dynamodb+cdc://. On the egress side, towards CrateDB, it will use thedata/auxcolumn strategy.It doesn't mean it's not cloud-ready, it is just more universal, because it can be used both in an ad hoc / standalone operations mode, in development sandboxes, and can also be invoked on any other managed Python environment, at your disposal.
Backlog I
create_stream,iterator_type,sleep_time_no_records, etc.Backlog II
See DynamoDB: General backlog #231.
/cc @juanpardo, @hlcianfagna, @hammerhead, @wierdvanderhaar, @karynzv