You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It seems that the version 4.0.0 of the library removes support of native DynamoDB Streams.
My understanding is that this is caused by the migration to KCL v2 that doesn't support it either.
The Kinesis Binder does not support DynamoDB Streams Adapter any more. There is no its implementation for SDK v2 and general AWS recommendation is to use Kinesis enabled on the table to captures data changes.
Will it be possible to elaborate a bit on where these recommendations are coming from and what are the alternatives for applications that are strongly dependent on native DynamoDB Streams core features? Thanks in advance 👍
For a bit of extra context, here are a few key differences between native DynamoDB Streams and DynamoDB integration with Kinesis to implement change streams that are important for some use-cases and might have be overlooked when deprecating the support of native DynamoDB Streams:
The Kinesis data stream records might appear in a different sequence than the item changes occurred. The same item notifications might also appear more than once in the stream. You can check the ApproximateCreationDateTime attribute to identify the approximate order that the item modifications occurred, and to identify duplicate records. ApproximateCreationDateTime indicates the time of the modification in milliseconds.
The text was updated successfully, but these errors were encountered:
We will be happy to bring that adapter support back when its version for AWS SDK v2 is released.
And that is exactly a matter of the issue on AWS Lab side: awslabs/dynamodb-streams-kinesis-adapter#22.
Until then we just cannot have both AWS SDK v1 & v2 on classpath.
Plus as you know the KCL v2 cannot interact with that DynamoDB Streams v1.
It seems that the version 4.0.0 of the library removes support of native DynamoDB Streams.
My understanding is that this is caused by the migration to KCL v2 that doesn't support it either.
The release notes are suggesting:
Will it be possible to elaborate a bit on where these recommendations are coming from and what are the alternatives for applications that are strongly dependent on native DynamoDB Streams core features? Thanks in advance 👍
For a bit of extra context, here are a few key differences between native DynamoDB Streams and DynamoDB integration with Kinesis to implement change streams that are important for some use-cases and might have be overlooked when deprecating the support of native DynamoDB Streams:
Change data capture for DynamoDB Streams:
Kinesis Data Streams to capture changes to DynamoDB:
The text was updated successfully, but these errors were encountered: