Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Added Support for Time based iterators #94

Merged
merged 1 commit into from
Aug 11, 2016

Conversation

pfifer
Copy link
Contributor

@pfifer pfifer commented Aug 11, 2016

Preliminary Release Notes

  • Add support for time based iterators (See GetShardIterator Documentation)
    The KinesisClientLibConfiguration now supports providing an initial time stamp position.
    • This position is only used if there is no current checkpoint for the shard.
    • This setting cannot be used with DynamoDB Streams
      Resolves Issue #88

@pfifer pfifer added this to the v1.7.0 milestone Aug 11, 2016
Added support for time based iterators.  Time based iterators are only
used if there is no current checkpoint for that shard, otherwise the
sequence number of the checkpoint is used.
@pfifer pfifer force-pushed the time-based-iterators branch from 63a0828 to aa47fce Compare August 11, 2016 16:20
@pfifer pfifer merged commit 33e37ef into awslabs:master Aug 11, 2016
pfifer added a commit that referenced this pull request Aug 22, 2016
* Add support for time based iterators ([See GetShardIterator Documentation](http://docs.aws.amazon.com/kinesis/latest/APIReference/API_GetShardIterator.html))
  * [PR #94](#94)
  The `KinesisClientLibConfiguration` now supports providing an initial time stamp position.
  * This position is only used if there is no current checkpoint for the shard.
  * This setting cannot be used with DynamoDB Streams
  Resolves [Issue #88](#88)
* Allow Prioritization of Parent Shards for Task Assignment
  * [PR #95](#95)
  The `KinesisClientLibconfiguration` now supports providing a `ShardPrioritization` strategy.  This strategy controls how the `Worker` determines which `ShardConsumer` to call next.  This can improve processing for streams that split often, such as DynamoDB Streams.
* Remove direct dependency on `aws-java-sdk-core`, to allow independent versioning.
  * [PR #92](#92)
  **You may need to add a direct dependency on aws-java-sdk-core if other dependencies include an older version.**
@pfifer pfifer deleted the time-based-iterators branch June 22, 2017 14:08
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant