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.

Sign up for GitHub

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

Jump to bottom

Support AT_TIMESTAMP #88

Closed
Dinduks opened this issue Jul 18, 2016 · 2 comments
Closed

Support AT_TIMESTAMP #88

Dinduks opened this issue Jul 18, 2016 · 2 comments

Comments

@Dinduks
Copy link

Dinduks commented Jul 18, 2016

Hi,

We want to specify a timestamp as a InitialPositionInStream so we can read from a specific point in time.
This feature is apparently currently unavailable and we'd like to add it to KCL.

It could look like this for example:

clientLibConfiguration.withInitialPositionInStream(InitialPositionInStream.AT_TIMESTAMP)
    .withTimestamp(1234)

What do you think about this and what part of the code should I start looking into?

Thank you!
@pfifer
Copy link
Contributor

pfifer commented Aug 11, 2016

I'm in the process of merging an internal change, and this should be coming soon.

@pfifer pfifer mentioned this issue Aug 11, 2016
Merged
@Dinduks
Copy link
Author

Dinduks commented Aug 16, 2016

Thanks @pfifer!
Any ETA for 1.7.0?

pfifer added a commit that referenced this issue Aug 22, 2016
@pfifer
Version 1.7.0 of the Amazon Kinesis Client Library
8a32e89 
* 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 mentioned this issue Oct 26, 2016
Closed
@jweinsteincbt jweinsteincbt mentioned this issue Mar 2, 2017
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@Dinduks @pfifer