make getBytesPerReducer support human readable values like 128m and 1g#1436
Merged
rubanm merged 1 commit intotwitter:developfrom Sep 4, 2015
Merged
make getBytesPerReducer support human readable values like 128m and 1g#1436rubanm merged 1 commit intotwitter:developfrom
rubanm merged 1 commit intotwitter:developfrom
Conversation
Contributor
|
@epishkin looks good. Thanks. |
rubanm
added a commit
that referenced
this pull request
Sep 4, 2015
make getBytesPerReducer support human readable values like 128m and 1g
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Supported formats are
longor human readable format.For human readable format you can use the following suffix (case insensitive): k(kilo), m(mega), g(giga), t(tera), p(peta), e(exa).
Examples: 1024, 128m, 1g.
@bholt @sid-kap @sagemintblue @rubanm guys could you review?