Revert "Merge branch 'feature/nodetool-zero-arg-rpc' into develop" [JIRA: TOOLS-130] #156
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
+1 |
kellymclaughlin
added a commit
that referenced
this pull request
Jul 28, 2014
Revert "Merge branch 'feature/nodetool-zero-arg-rpc' into develop"
|
create jira issue |
Basho-JIRA
changed the title
ksauzz
changed the title
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This reverts commit 93db72e, reversing
changes made to a56fe9b.
After looking more into this and thinking about what it would take to bring
riak-adminup to speed to work in mixed cluster scenarios up until the point where people are no longer upgrading to some future version from 2.0 (i.e. a few years down the road) I am not sure it is worth the effort. This reverts the previousnode_packagechange as the path of least resistance.