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 2018/08/01 13:31:00 UTC

[jira] [Resolved] (FLINK-9926) Allow for ShardConsumer override in Kinesis consumer

     [ https://issues.apache.org/jira/browse/FLINK-9926?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Tzu-Li (Gordon) Tai resolved FLINK-9926.
----------------------------------------
       Resolution: Fixed
    Fix Version/s: 1.6.0

Merged.

1.7.0: dd4b3d1fd3de9c64d077c67bcf740ba347e81a3a
1.6.0: 208057654f80aa303fc69938264d71d729b02cf8

> Allow for ShardConsumer override in Kinesis consumer
> ----------------------------------------------------
>
>                 Key: FLINK-9926
>                 URL: https://issues.apache.org/jira/browse/FLINK-9926
>             Project: Flink
>          Issue Type: Task
>          Components: Kinesis Connector
>            Reporter: Thomas Weise
>            Assignee: Thomas Weise
>            Priority: Minor
>              Labels: pull-request-available
>             Fix For: 1.6.0
>
>
> There are various reasons why the user may want to override the consumer. Examples are to optimize the run loop or to add additional metrics or logging. Instead of baking the constructor into runFetcher, create a customizable factory method.
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)