[jira] [Commented] (FLINK-3230) Kinesis streaming producer

["ASF GitHub Bot (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/FLINK-3230?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15247437#comment-15247437 ] 

ASF GitHub Bot commented on FLINK-3230:
---------------------------------------

GitHub user rmetzger opened a pull request:

    https://github.com/apache/flink/pull/1910

    [FLINK-3230] Add producer for Amazon Kinesis Streams into Flink

    I've tested this connector against two kinesis streams. Since Kinesis is a hosted service, I can not implement a full integration test that runs with each test.
    I'll run further tests once we've added a Kinesis consumer as well.

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/rmetzger/flink flink3230

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/flink/pull/1910.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #1910
    
----
commit 0f6fc06b2dce5c5dbaae32ba0955417c5b029fbf
Author: Robert Metzger <rm...@apache.org>
Date:   2016-04-11T14:48:54Z

    [FLINK-3230] Add producer for Amazon Kinesis Streams into Flink

----


> Kinesis streaming producer
> --------------------------
>
>                 Key: FLINK-3230
>                 URL: https://issues.apache.org/jira/browse/FLINK-3230
>             Project: Flink
>          Issue Type: Sub-task
>          Components: Streaming Connectors
>            Reporter: Tzu-Li (Gordon) Tai
>            Assignee: Robert Metzger
>
> Add a FlinkKinesisProducer for the Flink Kinesis streaming connector. We will be using AWS SDK implementation for code consistency with the FlinkKinesisConsumer.
> The features of FlinkKinesisProducer is rather straightforward:
> 1. Partition put records based on partition key.
> 2. Configurable put mode: Bulk put for higher throughput vs. sequential single record puts. Size of bulk should also be configurable.
> 3. For bulk put, user can also choose to enforce strict ordering of the result with the tradeoff of higher put latency. Ref: https://brandur.org/kinesis-order



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)