[
https://issues.apache.org/jira/browse/HADOOP-13680?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15601522#comment-15601522
]
ASF GitHub Bot commented on HADOOP-13680:
-----------------------------------------
GitHub user steveloughran opened a pull request:
https://github.com/apache/hadoop/pull/145
Steve's patch for '13680 get long bytes
This for HADOOP-13680; just naming it so that yetus does *not* give it
priority over the other PR
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/steveloughran/hadoop
s3/HADOOP-13680-get-long-bytes
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/hadoop/pull/145.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #145
----
commit 681e412c7d59e5bc83702b2dc3715da8054b02f4
Author: Steve Loughran <ste...@apache.org>
Date: 2016-10-24T09:58:47Z
HADOOP-13680 get long bytes
----
> fs.s3a.readahead.range to use getLongBytes
> ------------------------------------------
>
> Key: HADOOP-13680
> URL: https://issues.apache.org/jira/browse/HADOOP-13680
> Project: Hadoop Common
> Issue Type: Sub-task
> Components: fs/s3
> Affects Versions: 2.8.0
> Reporter: Steve Loughran
>
> The {{fs.s3a.readahead.range}} value is measured in bytes, but can be
> hundreds of KB. Easier to use getLongBytes and set to things like "300k"
> This will be backwards compatible with the existing settings if anyone is
> using them, because the no-prefix default will still be bytes
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: common-issues-h...@hadoop.apache.org
