[
https://issues.apache.org/jira/browse/FLINK-4582?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tzu-Li (Gordon) Tai updated FLINK-4582:
---------------------------------------
Description:
AWS DynamoDB is a NoSQL database service that has a CDC-like (change data
capture) feature called DynamoDB Streams
(http://docs.aws.amazon.com/amazondynamodb/latest/developerguide/Streams.html),
which is a stream feed of item-level table activities.
The DynamoDB Streams shard abstraction follows that of Kinesis Streams with
only a slight difference in resharding behaviours, so it is possible to build
on the internals of our Flink Kinesis Consumer for an exactly-once DynamoDB
Streams source.
I propose an API something like this:
{code}
DataStream dynamoItemsCdc =
FlinkKinesisConsumer.asDynamoDBStream(tableNames, schema, config)
{code}
The feature adds more connectivity to popular AWS services for Flink, and
combining what Flink has for exactly-once semantics, out-of-core state
backends, and queryable state with CDC can have very strong use cases. For this
feature there should only be an extra dependency to the AWS Java SDK for
DynamoDB, which has Apache License 2.0.
was:
AWS DynamoDB is a NoSQL database service that has a CDC-like (change data
capture) feature called DynamoDB Streams
(http://docs.aws.amazon.com/amazondynamodb/latest/developerguide/Streams.html),
which is a stream feed of item-level table activities.
The DynamoDB Streams shard abstraction follows that of Kinesis Streams with
only a slight difference in resharding behaviours, so it is possible to build
on the internals of our Flink Kinesis Consumer for an exactly-once DynamoDB
Streams source.
I propose an API something like this:
{code}
DataStream dynamoItemsCdc =
FlinkKinesisConsumer.asDynamoDBStream(tableNames, schema, config)
{code}
The feature adds more connectivity to popular AWS services for Flink, and
combining what Flink has for exactly-once semantics and out-of-core state
backends with CDC can have very strong use cases. For this feature there should
only be an extra dependency to the AWS Java SDK for DynamoDB, which has Apache
License 2.0.
> Allow FlinkKinesisConsumer to adapt for AWS DynamoDB Streams
> ------------------------------------------------------------
>
> Key: FLINK-4582
> URL: https://issues.apache.org/jira/browse/FLINK-4582
> Project: Flink
> Issue Type: New Feature
> Components: Kinesis Connector, Streaming Connectors
> Reporter: Tzu-Li (Gordon) Tai
> Fix For: 1.2.0
>
>
> AWS DynamoDB is a NoSQL database service that has a CDC-like (change data
> capture) feature called DynamoDB Streams
> (http://docs.aws.amazon.com/amazondynamodb/latest/developerguide/Streams.html),
> which is a stream feed of item-level table activities.
> The DynamoDB Streams shard abstraction follows that of Kinesis Streams with
> only a slight difference in resharding behaviours, so it is possible to build
> on the internals of our Flink Kinesis Consumer for an exactly-once DynamoDB
> Streams source.
> I propose an API something like this:
> {code}
> DataStream dynamoItemsCdc =
> FlinkKinesisConsumer.asDynamoDBStream(tableNames, schema, config)
> {code}
> The feature adds more connectivity to popular AWS services for Flink, and
> combining what Flink has for exactly-once semantics, out-of-core state
> backends, and queryable state with CDC can have very strong use cases. For
> this feature there should only be an extra dependency to the AWS Java SDK for
> DynamoDB, which has Apache License 2.0.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
