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

Make ShardInfo Public, and Update Documentation #127

Merged
merged 1 commit into from
Jan 9, 2017

Conversation

pfifer
Copy link
Contributor

@pfifer pfifer commented Jan 9, 2017

Made the ShardInfo class public, and updated the documentation for a
number of the properties.

This will allow users to implement custom shard prioritization
strategies.

Fixes:
Issue #120

Made the ShardInfo class public, and updated the documentation for a
number of the properties.

This will allow users to implement custom shard prioritization
strategies.

Fixes:
Issue awslabs#120
@pfifer pfifer added this to the Release 1.7.3 milestone Jan 9, 2017
@pfifer pfifer merged commit a7b16b4 into awslabs:master Jan 9, 2017
@pfifer pfifer deleted the shard-info-fix branch January 9, 2017 16:11
pfifer added a commit to pfifer/amazon-kinesis-client that referenced this pull request Jan 20, 2017
* Upgrade to the newest AWS Java SDK.
  * Issue awslabs/amazon-kinesis-client-python#27
  * PR awslabs#126
  * PR awslabs#125
* Added a direct dependency on commons-logging.
  * Issue awslabs#123
  * PR awslabs#124
* Make ShardInfo public to allow for custom ShardPrioritization strategies.
  * Issue awslabs#120
  * PR awslabs#127
pfifer added a commit that referenced this pull request Jan 20, 2017
* Upgrade to the newest AWS Java SDK.
  * Issue awslabs/amazon-kinesis-client-python#27
  * PR #126
  * PR #125
* Added a direct dependency on commons-logging.
  * Issue #123
  * PR #124
* Make ShardInfo public to allow for custom ShardPrioritization strategies.
  * Issue #120
  * PR #127
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