You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Tzu-Li (Gordon) Tai (JIRA)" <ji...@apache.org> on 2016/09/06 13:07:20 UTC
[jira] [Created] (FLINK-4582) Allow FlinkKinesisConsumer to adapt
for AWS DynamoDB Streams
Tzu-Li (Gordon) Tai created FLINK-4582:
------------------------------------------
Summary: 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 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.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)