Hi,

The Kinesis consumer currently does not emit watermarks, and this can lead
to problems when a single subtask reads from multiple shards and offsets
are not closely aligned with respect to the event time.

The Kafka consumer has support for periodic and punctuated watermarks,
although there is also the unresolved issue
https://issues.apache.org/jira/browse/FLINK-5479 that would equally apply
for Kinesis.

I propose adding support for timestamp assigner and watermark generator to
the Kinesis consumer.

As for handling of idle shards, is there a preference? Perhaps a
customization point on the assigner that defers the decision to the user
would be appropriate?

Thanks,
Thomas

Reply via email to