-
Notifications
You must be signed in to change notification settings - Fork 93
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
Dynomite api support #160
base: master
Are you sure you want to change the base?
Dynomite api support #160
Conversation
@tiodollar this seems to fail the test cases. Any idea why? What is the case that this is needed? |
@ipapapa With the merge, All checks have passed. |
@@ -123,6 +123,12 @@ public AbstractTokenMapSupplier(int port) { | |||
localDatacenter = ConfigUtils.getDataCenter(); | |||
unsuppliedPort = port; | |||
} | |||
|
|||
public AbstractTokenMapSupplier(int port,String localZone,String localDatacenter) { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why do we need this extra constructor? I do not see it being used in this PR.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It would be nice to add a few test cases to make sure that we have proper coverage as this is a new feature. I believe we have the HTTP based token map supplier tests that you can leverage. An example would be to create an exemplary JSON response from Dynomite and use that as the basis for testing.
Added support to dynomite REST API to search the cluester tokens https://github.com/Netflix/dynomite/wiki/REST.