Skip to content Skip to sidebar Skip to footer

Read From Kinesis Is Giving Empty Records When Run Using Previous Sequence Number Or Timestamp

I am trying to read the messages pushed to Kinesis stream with the help of get_records() and get_shard_iterator() APIs. My producer keeps pushing the records when processed at i

Solution 1:

As per my discussion with AWS technical support person, there can be a few messages with empty records and hence it is not a good idea to break when len(get_response['Records']) == 0.

The better approach suggested was - we can have a counter indicating maximum number of messages that you read in a run and exit loop after reading as many messages.

Post a Comment for "Read From Kinesis Is Giving Empty Records When Run Using Previous Sequence Number Or Timestamp"