[FLINK-29395][Connector/Kinesis] Handle empty deaggregated records in… #21002
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
…FanOutRecordPublisher
What is the purpose of the change
Cherry-pick of https://github.com/apache/flink/pull/20945/files
The consumer fails when three conditions are met:
This can happen when the user writes aggregated records into their Kinesis stream whilst specifying the explicitHashKey for every single user record. When resharding occurs, there is a possibility that records within the same aggregated batch fall into two different shards, since they have different explicit hash keys. When this happens, the deaggregated records are dropped. (We need to do this in Kinesis Consumer so we do not process duplicate records. See awslabs/kinesis-aggregation#11)
If all deaggregated records are dropped, the consumer receives an empty deaggregated record batch even though the record batch is not empty.
Brief change log
This is fixed by returning the AT_TIMESTAMP starting position when receiving an AT_TIMESTAMP sentinel sequence number.
Verifying this change
Does this pull request potentially affect one of the following parts:
@Public(Evolving)
: noDocumentation