flink-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (FLINK-5697) Add per-shard watermarks for FlinkKinesisConsumer
Date Thu, 01 Nov 2018 22:20:00 GMT

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

ASF GitHub Bot commented on FLINK-5697:

tweise commented on issue #6980: [FLINK-5697] [kinesis] Add periodic per-shard watermark support
URL: https://github.com/apache/flink/pull/6980#issuecomment-435206371
   @EronWright that's correct and I will make sure to document this. Even our planned follow-up
work won't be able to address such resharding scenario. I think we will only be able to address
that with the new source design that is currently under discussion (which should permit centralized
discovery and more sophisticated splitting/shard distribution).  

This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:

> Add per-shard watermarks for FlinkKinesisConsumer
> -------------------------------------------------
>                 Key: FLINK-5697
>                 URL: https://issues.apache.org/jira/browse/FLINK-5697
>             Project: Flink
>          Issue Type: New Feature
>          Components: Kinesis Connector, Streaming Connectors
>            Reporter: Tzu-Li (Gordon) Tai
>            Assignee: Thomas Weise
>            Priority: Major
>              Labels: pull-request-available
> It would be nice to let the Kinesis consumer be on-par in functionality with the Kafka
consumer, since they share very similar abstractions. Per-partition / shard watermarks is
something we can add also to the Kinesis consumer.

This message was sent by Atlassian JIRA

View raw message