[CAMEL-12089] Camel-AWS: Kinesis consumer starts consuming data from the beginning even though the shard is in Closed state

• Type: Improvement
• Status: Resolved
• Priority: Minor
• Resolution: Fixed
• Fix Version/s: 2.21.0
• Component/s: camel-aws
• Estimated Complexity: Unknown
• Assignee: Andrea Cosentino
• Reporter: Andrea Cosentino
• Created: 18/Dec/17 10:16
• Updated: 21/Dec/17 08:56
• Resolved: 21/Dec/17 08:56

Description

We may think to add an option shardClosed to choose the behavior in case the shard is closed

We will have an enum with the following values:

• ignore = default behavior
• fail = throw an exception
• silent = ignore but without any logging

A restart option is not needed because in case we decide to go with ignore or silent the behavior will be the same as restart.