[jira] [Commented] (HADOOP-11731) Rework the changelog and releasenotes
[
https://issues.apache.org/jira/browse/HADOOP-11731?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14374781#comment-14374781
]
Hadoop QA commented on HADOOP-11731:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12706363/HADOOP-11731-03.patch
against trunk revision 4335429.
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+0 tests included{color}. The patch appears to be a
documentation patch that doesn't require tests.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 javadoc{color}. There were no new javadoc warning messages.
{color:green}+1 eclipse:eclipse{color}. The patch built with
eclipse:eclipse.
{color:green}+1 findbugs{color}. The patch does not introduce any new
Findbugs (version 2.0.3) warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:red}-1 core tests{color}. The following test timeouts occurred in
hadoop-common-project/hadoop-common:
org.apache.hadoop.http.TestHttpServerLifecycle
Test results:
https://builds.apache.org/job/PreCommit-HADOOP-Build/5981//testReport/
Console output:
https://builds.apache.org/job/PreCommit-HADOOP-Build/5981//console
This message is automatically generated.
> Rework the changelog and releasenotes
> -
>
> Key: HADOOP-11731
> URL: https://issues.apache.org/jira/browse/HADOOP-11731
> Project: Hadoop Common
> Issue Type: New Feature
> Components: documentation
>Affects Versions: 3.0.0
>Reporter: Allen Wittenauer
> Attachments: HADOOP-11731-00.patch, HADOOP-11731-01.patch,
> HADOOP-11731-03.patch
>
>
> The current way we generate these build artifacts is awful. Plus they are
> ugly and, in the case of release notes, very hard to pick out what is
> important.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (HADOOP-11731) Rework the changelog and releasenotes
[ https://issues.apache.org/jira/browse/HADOOP-11731?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14374766#comment-14374766 ] Allen Wittenauer commented on HADOOP-11731: --- Making HADOOP-11553 as a conflicting patch since they touch the same pom.xml in the same place. > Rework the changelog and releasenotes > - > > Key: HADOOP-11731 > URL: https://issues.apache.org/jira/browse/HADOOP-11731 > Project: Hadoop Common > Issue Type: New Feature > Components: documentation >Affects Versions: 3.0.0 >Reporter: Allen Wittenauer > Attachments: HADOOP-11731-00.patch, HADOOP-11731-01.patch, > HADOOP-11731-03.patch > > > The current way we generate these build artifacts is awful. Plus they are > ugly and, in the case of release notes, very hard to pick out what is > important. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HADOOP-11553) Formalize the shell API
[ https://issues.apache.org/jira/browse/HADOOP-11553?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14374765#comment-14374765 ] Allen Wittenauer commented on HADOOP-11553: --- Making HADOOP-11731 as a conflicting patch since they touch the same pom.xml in the same place. > Formalize the shell API > --- > > Key: HADOOP-11553 > URL: https://issues.apache.org/jira/browse/HADOOP-11553 > Project: Hadoop Common > Issue Type: Improvement > Components: documentation, scripts >Affects Versions: 3.0.0 >Reporter: Allen Wittenauer >Assignee: Allen Wittenauer >Priority: Blocker > Attachments: HADOOP-11553-00.patch, HADOOP-11553-01.patch, > HADOOP-11553-02.patch, HADOOP-11553-03.patch > > > After HADOOP-11485, we need to formally document functions and environment > variables that 3rd parties can expect to be able to exist/use. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HADOOP-11731) Rework the changelog and releasenotes
[ https://issues.apache.org/jira/browse/HADOOP-11731?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Allen Wittenauer updated HADOOP-11731: -- Status: Patch Available (was: Open) > Rework the changelog and releasenotes > - > > Key: HADOOP-11731 > URL: https://issues.apache.org/jira/browse/HADOOP-11731 > Project: Hadoop Common > Issue Type: New Feature > Components: documentation >Affects Versions: 3.0.0 >Reporter: Allen Wittenauer > Attachments: HADOOP-11731-00.patch, HADOOP-11731-01.patch, > HADOOP-11731-03.patch > > > The current way we generate these build artifacts is awful. Plus they are > ugly and, in the case of release notes, very hard to pick out what is > important. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HADOOP-11731) Rework the changelog and releasenotes
[ https://issues.apache.org/jira/browse/HADOOP-11731?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Allen Wittenauer updated HADOOP-11731: -- Attachment: HADOOP-11731-03.patch -03: * only create master versions during build * tie them into site.xml * move the creation to hadoop-common > Rework the changelog and releasenotes > - > > Key: HADOOP-11731 > URL: https://issues.apache.org/jira/browse/HADOOP-11731 > Project: Hadoop Common > Issue Type: New Feature > Components: documentation >Affects Versions: 3.0.0 >Reporter: Allen Wittenauer > Attachments: HADOOP-11731-00.patch, HADOOP-11731-01.patch, > HADOOP-11731-03.patch > > > The current way we generate these build artifacts is awful. Plus they are > ugly and, in the case of release notes, very hard to pick out what is > important. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HADOOP-11731) Rework the changelog and releasenotes
[ https://issues.apache.org/jira/browse/HADOOP-11731?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Allen Wittenauer updated HADOOP-11731: -- Status: Open (was: Patch Available) > Rework the changelog and releasenotes > - > > Key: HADOOP-11731 > URL: https://issues.apache.org/jira/browse/HADOOP-11731 > Project: Hadoop Common > Issue Type: New Feature > Components: documentation >Affects Versions: 3.0.0 >Reporter: Allen Wittenauer > Attachments: HADOOP-11731-00.patch, HADOOP-11731-01.patch > > > The current way we generate these build artifacts is awful. Plus they are > ugly and, in the case of release notes, very hard to pick out what is > important. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HADOOP-10895) HTTP KerberosAuthenticator fallback should have a flag to disable it
[
https://issues.apache.org/jira/browse/HADOOP-10895?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14374750#comment-14374750
]
Yongjun Zhang commented on HADOOP-10895:
Hi [~vinodkv],
As the release notes stated, it has to be an incompatible change because
relevant application code (oozie for example, and [~rkanter] has raised the
concern before) need to be changed accordingly.
Thanks.
> HTTP KerberosAuthenticator fallback should have a flag to disable it
>
>
> Key: HADOOP-10895
> URL: https://issues.apache.org/jira/browse/HADOOP-10895
> Project: Hadoop Common
> Issue Type: Bug
> Components: security
>Affects Versions: 2.4.1
>Reporter: Alejandro Abdelnur
>Assignee: Yongjun Zhang
>Priority: Blocker
> Attachments: HADOOP-10895.001.patch, HADOOP-10895.002.patch,
> HADOOP-10895.003.patch, HADOOP-10895.003v1.patch, HADOOP-10895.003v2.patch,
> HADOOP-10895.003v2improved.patch, HADOOP-10895.004.patch,
> HADOOP-10895.005.patch, HADOOP-10895.006.patch, HADOOP-10895.007.patch,
> HADOOP-10895.008.patch, HADOOP-10895.009.patch
>
>
> Per review feedback in HADOOP-10771, {{KerberosAuthenticator}} and the
> delegation token version coming in with HADOOP-10771 should have a flag to
> disable fallback to pseudo, similarly to the one that was introduced in
> Hadoop RPC client with HADOOP-9698.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (HADOOP-11731) Rework the changelog and releasenotes
[
https://issues.apache.org/jira/browse/HADOOP-11731?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14373021#comment-14373021
]
Hadoop QA commented on HADOOP-11731:
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12706187/HADOOP-11731-01.patch
against trunk revision e1feb4e.
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+0 tests included{color}. The patch appears to be a
documentation patch that doesn't require tests.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 javadoc{color}. There were no new javadoc warning messages.
{color:green}+1 eclipse:eclipse{color}. The patch built with
eclipse:eclipse.
{color:green}+1 findbugs{color}. The patch does not introduce any new
Findbugs (version 2.0.3) warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in .
Test results:
https://builds.apache.org/job/PreCommit-HADOOP-Build/5980//testReport/
Console output:
https://builds.apache.org/job/PreCommit-HADOOP-Build/5980//console
This message is automatically generated.
> Rework the changelog and releasenotes
> -
>
> Key: HADOOP-11731
> URL: https://issues.apache.org/jira/browse/HADOOP-11731
> Project: Hadoop Common
> Issue Type: New Feature
> Components: documentation
>Affects Versions: 3.0.0
>Reporter: Allen Wittenauer
> Attachments: HADOOP-11731-00.patch, HADOOP-11731-01.patch
>
>
> The current way we generate these build artifacts is awful. Plus they are
> ugly and, in the case of release notes, very hard to pick out what is
> important.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (HADOOP-10400) Incorporate new S3A FileSystem implementation
[
https://issues.apache.org/jira/browse/HADOOP-10400?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Steve Loughran updated HADOOP-10400:
Assignee: Jordan Mendelson
> Incorporate new S3A FileSystem implementation
> -
>
> Key: HADOOP-10400
> URL: https://issues.apache.org/jira/browse/HADOOP-10400
> Project: Hadoop Common
> Issue Type: New Feature
> Components: fs, fs/s3
>Affects Versions: 2.4.0
>Reporter: Jordan Mendelson
>Assignee: Jordan Mendelson
> Fix For: 2.6.0
>
> Attachments: HADOOP-10400-1.patch, HADOOP-10400-2.patch,
> HADOOP-10400-3.patch, HADOOP-10400-4.patch, HADOOP-10400-5.patch,
> HADOOP-10400-6.patch, HADOOP-10400-7.patch, HADOOP-10400-8-branch-2.patch,
> HADOOP-10400-8.patch, HADOOP-10400-branch-2.patch
>
>
> The s3native filesystem has a number of limitations (some of which were
> recently fixed by HADOOP-9454). This patch adds an s3a filesystem which uses
> the aws-sdk instead of the jets3t library. There are a number of improvements
> over s3native including:
> - Parallel copy (rename) support (dramatically speeds up commits on large
> files)
> - AWS S3 explorer compatible empty directories files "xyz/" instead of
> "xyz_$folder$" (reduces littering)
> - Ignores s3native created _$folder$ files created by s3native and other S3
> browsing utilities
> - Supports multiple output buffer dirs to even out IO when uploading files
> - Supports IAM role-based authentication
> - Allows setting a default canned ACL for uploads (public, private, etc.)
> - Better error recovery handling
> - Should handle input seeks without having to download the whole file (used
> for splits a lot)
> This code is a copy of https://github.com/Aloisius/hadoop-s3a with patches to
> various pom files to get it to build against trunk. I've been using 0.0.1 in
> production with CDH 4 for several months and CDH 5 for a few days. The
> version here is 0.0.2 which changes around some keys to hopefully bring the
> key name style more inline with the rest of hadoop 2.x.
> *Tunable parameters:*
> fs.s3a.access.key - Your AWS access key ID (omit for role authentication)
> fs.s3a.secret.key - Your AWS secret key (omit for role authentication)
> fs.s3a.connection.maximum - Controls how many parallel connections
> HttpClient spawns (default: 15)
> fs.s3a.connection.ssl.enabled - Enables or disables SSL connections to S3
> (default: true)
> fs.s3a.attempts.maximum - How many times we should retry commands on
> transient errors (default: 10)
> fs.s3a.connection.timeout - Socket connect timeout (default: 5000)
> fs.s3a.paging.maximum - How many keys to request from S3 when doing
> directory listings at a time (default: 5000)
> fs.s3a.multipart.size - How big (in bytes) to split a upload or copy
> operation up into (default: 104857600)
> fs.s3a.multipart.threshold - Until a file is this large (in bytes), use
> non-parallel upload (default: 2147483647)
> fs.s3a.acl.default - Set a canned ACL on newly created/copied objects
> (private | public-read | public-read-write | authenticated-read |
> log-delivery-write | bucket-owner-read | bucket-owner-full-control)
> fs.s3a.multipart.purge - True if you want to purge existing multipart
> uploads that may not have been completed/aborted correctly (default: false)
> fs.s3a.multipart.purge.age - Minimum age in seconds of multipart uploads
> to purge (default: 86400)
> fs.s3a.buffer.dir - Comma separated list of directories that will be used
> to buffer file writes out of (default: uses ${hadoop.tmp.dir}/s3a )
> *Caveats*:
> Hadoop uses a standard output committer which uploads files as
> filename.COPYING before renaming them. This can cause unnecessary performance
> issues with S3 because it does not have a rename operation and S3 already
> verifies uploads against an md5 that the driver sets on the upload request.
> While this FileSystem should be significantly faster than the built-in
> s3native driver because of parallel copy support, you may want to consider
> setting a null output committer on our jobs to further improve performance.
> Because S3 requires the file length and MD5 to be known before a file is
> uploaded, all output is buffered out to a temporary file first similar to the
> s3native driver.
> Due to the lack of native rename() for S3, renaming extremely large files or
> directories make take a while. Unfortunately, there is no way to notify
> hadoop that progress is still being made for rename operations, so your job
> may time out unless you increase the task timeout.
> This driver will fully ignore _$folder$ files. This was necessary so that it
> could interoperate with repositories that have had the s3native driver used
> on them, but means that it won't recognize em
[jira] [Updated] (HADOOP-11731) Rework the changelog and releasenotes
[ https://issues.apache.org/jira/browse/HADOOP-11731?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Allen Wittenauer updated HADOOP-11731: -- Status: Patch Available (was: Open) > Rework the changelog and releasenotes > - > > Key: HADOOP-11731 > URL: https://issues.apache.org/jira/browse/HADOOP-11731 > Project: Hadoop Common > Issue Type: New Feature > Components: documentation >Affects Versions: 3.0.0 >Reporter: Allen Wittenauer > Attachments: HADOOP-11731-00.patch, HADOOP-11731-01.patch > > > The current way we generate these build artifacts is awful. Plus they are > ugly and, in the case of release notes, very hard to pick out what is > important. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HADOOP-11731) Rework the changelog and releasenotes
[ https://issues.apache.org/jira/browse/HADOOP-11731?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Allen Wittenauer updated HADOOP-11731: -- Release Note: * The release notes now only contains JIRA issues with incompatible changes and actual release notes. The generated format has been changed from HTML to markdown. * The changelog is now automatically generated from data stored in JIRA rather than manually maintained. The format has been changed from pure text to markdown as well as containing more of the information that was previously stored in the release notes. * Site documentation generation now requires Python. was: * The release notes now only contains JIRA issues with incompatible changes and actual release notes. The generated format has been changed from HTML to markdown. * The changelog is now automatically generated from data stored in JIRA rather than manually maintained. The format has been changed from pure text to markdown as well as containing more of the information that was previously stored in the release notes. > Rework the changelog and releasenotes > - > > Key: HADOOP-11731 > URL: https://issues.apache.org/jira/browse/HADOOP-11731 > Project: Hadoop Common > Issue Type: New Feature > Components: documentation >Affects Versions: 3.0.0 >Reporter: Allen Wittenauer > Attachments: HADOOP-11731-00.patch, HADOOP-11731-01.patch > > > The current way we generate these build artifacts is awful. Plus they are > ugly and, in the case of release notes, very hard to pick out what is > important. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HADOOP-11731) Rework the changelog and releasenotes
[ https://issues.apache.org/jira/browse/HADOOP-11731?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Allen Wittenauer updated HADOOP-11731: -- Attachment: HADOOP-11731-01.patch -01: * Integrated into site documentation generation > Rework the changelog and releasenotes > - > > Key: HADOOP-11731 > URL: https://issues.apache.org/jira/browse/HADOOP-11731 > Project: Hadoop Common > Issue Type: New Feature > Components: documentation >Affects Versions: 3.0.0 >Reporter: Allen Wittenauer > Attachments: HADOOP-11731-00.patch, HADOOP-11731-01.patch > > > The current way we generate these build artifacts is awful. Plus they are > ugly and, in the case of release notes, very hard to pick out what is > important. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HADOOP-11553) Formalize the shell API
[
https://issues.apache.org/jira/browse/HADOOP-11553?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14372993#comment-14372993
]
Hadoop QA commented on HADOOP-11553:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12706185/HADOOP-11553-03.patch
against trunk revision e1feb4e.
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+0 tests included{color}. The patch appears to be a
documentation patch that doesn't require tests.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 javadoc{color}. There were no new javadoc warning messages.
{color:green}+1 eclipse:eclipse{color}. The patch built with
eclipse:eclipse.
{color:green}+1 findbugs{color}. The patch does not introduce any new
Findbugs (version 2.0.3) warnings.
{color:red}-1 release audit{color}. The applied patch generated 1
release audit warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in
hadoop-common-project/hadoop-common.
Test results:
https://builds.apache.org/job/PreCommit-HADOOP-Build/5979//testReport/
Release audit warnings:
https://builds.apache.org/job/PreCommit-HADOOP-Build/5979//artifact/patchprocess/patchReleaseAuditProblems.txt
Console output:
https://builds.apache.org/job/PreCommit-HADOOP-Build/5979//console
This message is automatically generated.
> Formalize the shell API
> ---
>
> Key: HADOOP-11553
> URL: https://issues.apache.org/jira/browse/HADOOP-11553
> Project: Hadoop Common
> Issue Type: Improvement
> Components: documentation, scripts
>Affects Versions: 3.0.0
>Reporter: Allen Wittenauer
>Assignee: Allen Wittenauer
>Priority: Blocker
> Attachments: HADOOP-11553-00.patch, HADOOP-11553-01.patch,
> HADOOP-11553-02.patch, HADOOP-11553-03.patch
>
>
> After HADOOP-11485, we need to formally document functions and environment
> variables that 3rd parties can expect to be able to exist/use.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (HADOOP-11553) Formalize the shell API
[ https://issues.apache.org/jira/browse/HADOOP-11553?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14372981#comment-14372981 ] Allen Wittenauer commented on HADOOP-11553: --- FWIW, I think this is getting very close to commit-able. It'd be good for someone to start looking this over > Formalize the shell API > --- > > Key: HADOOP-11553 > URL: https://issues.apache.org/jira/browse/HADOOP-11553 > Project: Hadoop Common > Issue Type: Improvement > Components: documentation, scripts >Affects Versions: 3.0.0 >Reporter: Allen Wittenauer >Assignee: Allen Wittenauer >Priority: Blocker > Attachments: HADOOP-11553-00.patch, HADOOP-11553-01.patch, > HADOOP-11553-02.patch, HADOOP-11553-03.patch > > > After HADOOP-11485, we need to formally document functions and environment > variables that 3rd parties can expect to be able to exist/use. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HADOOP-11326) documentation for configuring HVE: dfs.block.replicator.classname should be org.apache.hadoop.hdfs.server.blockmanagement.BlockPlacementPolicyWithNodeGroup
[ https://issues.apache.org/jira/browse/HADOOP-11326?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14372979#comment-14372979 ] Steve Loughran commented on HADOOP-11326: - Not Hortonworks .. JP did this @ VMWare... > documentation for configuring HVE: dfs.block.replicator.classname should be > org.apache.hadoop.hdfs.server.blockmanagement.BlockPlacementPolicyWithNodeGroup > --- > > Key: HADOOP-11326 > URL: https://issues.apache.org/jira/browse/HADOOP-11326 > Project: Hadoop Common > Issue Type: Bug > Components: documentation >Reporter: ellen johansen > > Attempted to create an HVE VM based cluster following the directions posted > here: > https://issues.apache.org/jira/secure/attachment/12551386/HVE%20User%20Guide%20on%20branch-1%28draft%20%29.pdf > > The doc has the value for dfs.block.replicator.classname set to > org.apache.hadoop.hdfs.server.namenode.BlockPlacementPolicyWithNodeGroup but > that class doesn't exist in hadoop 2.5, it seems that the class is > org.apache.hadoop.hdfs.server.blockmanagement.BlockPlacementPolicyWithNodeGroup > This JIRA is to request the documentation be updated. > thanks, -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HADOOP-11553) Formalize the shell API
[ https://issues.apache.org/jira/browse/HADOOP-11553?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Allen Wittenauer updated HADOOP-11553: -- Release Note: Python is now required to build the documentation. Hadoop Flags: Incompatible change > Formalize the shell API > --- > > Key: HADOOP-11553 > URL: https://issues.apache.org/jira/browse/HADOOP-11553 > Project: Hadoop Common > Issue Type: Improvement > Components: documentation, scripts >Affects Versions: 3.0.0 >Reporter: Allen Wittenauer >Assignee: Allen Wittenauer >Priority: Blocker > Attachments: HADOOP-11553-00.patch, HADOOP-11553-01.patch, > HADOOP-11553-02.patch, HADOOP-11553-03.patch > > > After HADOOP-11485, we need to formally document functions and environment > variables that 3rd parties can expect to be able to exist/use. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HADOOP-11553) Formalize the shell API
[ https://issues.apache.org/jira/browse/HADOOP-11553?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Allen Wittenauer updated HADOOP-11553: -- Status: Patch Available (was: Open) > Formalize the shell API > --- > > Key: HADOOP-11553 > URL: https://issues.apache.org/jira/browse/HADOOP-11553 > Project: Hadoop Common > Issue Type: Improvement > Components: documentation, scripts >Affects Versions: 3.0.0 >Reporter: Allen Wittenauer >Assignee: Allen Wittenauer >Priority: Blocker > Attachments: HADOOP-11553-00.patch, HADOOP-11553-01.patch, > HADOOP-11553-02.patch, HADOOP-11553-03.patch > > > After HADOOP-11485, we need to formally document functions and environment > variables that 3rd parties can expect to be able to exist/use. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HADOOP-11553) Formalize the shell API
[ https://issues.apache.org/jira/browse/HADOOP-11553?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Allen Wittenauer updated HADOOP-11553: -- Attachment: HADOOP-11553-03.patch -03: * Integrate shelldocmd.py into the build process. * Fix up some minor problems in pom.xml * shelldocmd.py now takes options, builds a toc, minor formatting fixes * moar dox > Formalize the shell API > --- > > Key: HADOOP-11553 > URL: https://issues.apache.org/jira/browse/HADOOP-11553 > Project: Hadoop Common > Issue Type: Improvement > Components: documentation, scripts >Affects Versions: 3.0.0 >Reporter: Allen Wittenauer >Assignee: Allen Wittenauer >Priority: Blocker > Attachments: HADOOP-11553-00.patch, HADOOP-11553-01.patch, > HADOOP-11553-02.patch, HADOOP-11553-03.patch > > > After HADOOP-11485, we need to formally document functions and environment > variables that 3rd parties can expect to be able to exist/use. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HADOOP-10895) HTTP KerberosAuthenticator fallback should have a flag to disable it
[
https://issues.apache.org/jira/browse/HADOOP-10895?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vinod Kumar Vavilapalli updated HADOOP-10895:
-
Target Version/s: 2.8.0 (was: 2.7.0)
Tx for the response [~yzhangal]. Moving this out to 2.8. while we discuss more.
I'll spend more time on this a bit later, but [~yzhangal], can you in the mean
while work with others to see if it *needs* to be an incompatible change?
Thanks.
> HTTP KerberosAuthenticator fallback should have a flag to disable it
>
>
> Key: HADOOP-10895
> URL: https://issues.apache.org/jira/browse/HADOOP-10895
> Project: Hadoop Common
> Issue Type: Bug
> Components: security
>Affects Versions: 2.4.1
>Reporter: Alejandro Abdelnur
>Assignee: Yongjun Zhang
>Priority: Blocker
> Attachments: HADOOP-10895.001.patch, HADOOP-10895.002.patch,
> HADOOP-10895.003.patch, HADOOP-10895.003v1.patch, HADOOP-10895.003v2.patch,
> HADOOP-10895.003v2improved.patch, HADOOP-10895.004.patch,
> HADOOP-10895.005.patch, HADOOP-10895.006.patch, HADOOP-10895.007.patch,
> HADOOP-10895.008.patch, HADOOP-10895.009.patch
>
>
> Per review feedback in HADOOP-10771, {{KerberosAuthenticator}} and the
> delegation token version coming in with HADOOP-10771 should have a flag to
> disable fallback to pseudo, similarly to the one that was introduced in
> Hadoop RPC client with HADOOP-9698.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (HADOOP-11735) hadoop-nfs’ pom.xml overrides mockito version but it’s the same as parent's
[
https://issues.apache.org/jira/browse/HADOOP-11735?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14372878#comment-14372878
]
Hadoop QA commented on HADOOP-11735:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12706166/HADOOP-11735.001.patch
against trunk revision e1feb4e.
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:red}-1 tests included{color}. The patch doesn't appear to include
any new or modified tests.
Please justify why no new tests are needed for this
patch.
Also please list what manual steps were performed to
verify this patch.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 javadoc{color}. There were no new javadoc warning messages.
{color:green}+1 eclipse:eclipse{color}. The patch built with
eclipse:eclipse.
{color:green}+1 findbugs{color}. The patch does not introduce any new
Findbugs (version 2.0.3) warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in
hadoop-common-project/hadoop-nfs.
Test results:
https://builds.apache.org/job/PreCommit-HADOOP-Build/5978//testReport/
Console output:
https://builds.apache.org/job/PreCommit-HADOOP-Build/5978//console
This message is automatically generated.
> hadoop-nfs’ pom.xml overrides mockito version but it’s the same as parent's
> ---
>
> Key: HADOOP-11735
> URL: https://issues.apache.org/jira/browse/HADOOP-11735
> Project: Hadoop Common
> Issue Type: Task
> Components: nfs
>Reporter: Kengo Seki
>Assignee: Kengo Seki
>Priority: Minor
> Attachments: HADOOP-11735.001.patch
>
>
> It should be removed because only hadoop-nfs will be left behind when parent
> upgrades mockito.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (HADOOP-11735) hadoop-nfs’ pom.xml overrides mockito version but it’s the same as parent's
[ https://issues.apache.org/jira/browse/HADOOP-11735?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kengo Seki updated HADOOP-11735: Status: Patch Available (was: Open) > hadoop-nfs’ pom.xml overrides mockito version but it’s the same as parent's > --- > > Key: HADOOP-11735 > URL: https://issues.apache.org/jira/browse/HADOOP-11735 > Project: Hadoop Common > Issue Type: Task > Components: nfs >Reporter: Kengo Seki >Assignee: Kengo Seki >Priority: Minor > Attachments: HADOOP-11735.001.patch > > > It should be removed because only hadoop-nfs will be left behind when parent > upgrades mockito. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (HADOOP-11735) hadoop-nfs’ pom.xml overrides mockito version but it’s the same as parent's
[ https://issues.apache.org/jira/browse/HADOOP-11735?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kengo Seki reassigned HADOOP-11735: --- Assignee: Kengo Seki > hadoop-nfs’ pom.xml overrides mockito version but it’s the same as parent's > --- > > Key: HADOOP-11735 > URL: https://issues.apache.org/jira/browse/HADOOP-11735 > Project: Hadoop Common > Issue Type: Task > Components: nfs >Reporter: Kengo Seki >Assignee: Kengo Seki >Priority: Minor > Attachments: HADOOP-11735.001.patch > > > It should be removed because only hadoop-nfs will be left behind when parent > upgrades mockito. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HADOOP-11735) hadoop-nfs’ pom.xml overrides mockito version but it’s the same as parent's
[ https://issues.apache.org/jira/browse/HADOOP-11735?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kengo Seki updated HADOOP-11735: Attachment: HADOOP-11735.001.patch > hadoop-nfs’ pom.xml overrides mockito version but it’s the same as parent's > --- > > Key: HADOOP-11735 > URL: https://issues.apache.org/jira/browse/HADOOP-11735 > Project: Hadoop Common > Issue Type: Task > Components: nfs >Reporter: Kengo Seki >Priority: Minor > Attachments: HADOOP-11735.001.patch > > > It should be removed because only hadoop-nfs will be left behind when parent > upgrades mockito. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (HADOOP-11735) hadoop-nfs’ pom.xml overrides mockito version but it’s the same as parent's
Kengo Seki created HADOOP-11735: --- Summary: hadoop-nfs’ pom.xml overrides mockito version but it’s the same as parent's Key: HADOOP-11735 URL: https://issues.apache.org/jira/browse/HADOOP-11735 Project: Hadoop Common Issue Type: Task Components: nfs Reporter: Kengo Seki Priority: Minor It should be removed because only hadoop-nfs will be left behind when parent upgrades mockito. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HADOOP-11709) Time.NANOSECONDS_PER_MILLISECOND - use class-level final constant instead of method variable
[
https://issues.apache.org/jira/browse/HADOOP-11709?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14372833#comment-14372833
]
Hudson commented on HADOOP-11709:
-
FAILURE: Integrated in Hadoop-Mapreduce-trunk-Java8 #139 (See
[https://builds.apache.org/job/Hadoop-Mapreduce-trunk-Java8/139/])
HADOOP-11709. Time.NANOSECONDS_PER_MILLISECOND - use class-level final constant
instead of method variable. Contributed by Ajith S. (ozawa: rev
43dde502b3be2133d62f1f074f016f35a56a7e2c)
*
hadoop-common-project/hadoop-common/src/main/java/org/apache/hadoop/util/Time.java
* hadoop-common-project/hadoop-common/CHANGES.txt
> Time.NANOSECONDS_PER_MILLISECOND - use class-level final constant instead of
> method variable
> -
>
> Key: HADOOP-11709
> URL: https://issues.apache.org/jira/browse/HADOOP-11709
> Project: Hadoop Common
> Issue Type: Improvement
>Reporter: Ajith S
>Assignee: Ajith S
>Priority: Trivial
> Labels: beginner, newbie
> Fix For: 2.8.0
>
> Attachments: 001-HDFS-7919.patch
>
>
> NANOSECONDS_PER_MILLISECOND constant can be moved to class level instead of
> creating it in each method call.
> {code}
> org.apache.hadoop.util.Time.java
> public static long monotonicNow() {
> final long NANOSECONDS_PER_MILLISECOND = 100;
> return System.nanoTime() / NANOSECONDS_PER_MILLISECOND;
> }
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (HADOOP-11447) Add a more meaningful toString method to SampleStat and MutableStat
[ https://issues.apache.org/jira/browse/HADOOP-11447?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14372826#comment-14372826 ] Hudson commented on HADOOP-11447: - FAILURE: Integrated in Hadoop-Mapreduce-trunk-Java8 #139 (See [https://builds.apache.org/job/Hadoop-Mapreduce-trunk-Java8/139/]) HADOOP-11447. Add a more meaningful toString method to SampleStat and MutableStat. (kasha) (kasha: rev fe5c23b670c773145b87fecfaf9191536e9f1c51) * hadoop-common-project/hadoop-common/src/main/java/org/apache/hadoop/metrics2/util/SampleStat.java * hadoop-common-project/hadoop-common/CHANGES.txt * hadoop-common-project/hadoop-common/src/main/java/org/apache/hadoop/metrics2/lib/MutableStat.java > Add a more meaningful toString method to SampleStat and MutableStat > --- > > Key: HADOOP-11447 > URL: https://issues.apache.org/jira/browse/HADOOP-11447 > Project: Hadoop Common > Issue Type: Improvement > Components: metrics >Affects Versions: 2.6.0 >Reporter: Karthik Kambatla >Assignee: Karthik Kambatla >Priority: Minor > Fix For: 2.8.0 > > Attachments: hadoop-11447-1.patch, hadoop-11447-2.patch > > > SampleStat and MutableStat don't override the toString method. A more > meaningful implementation could help with debugging. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HADOOP-11709) Time.NANOSECONDS_PER_MILLISECOND - use class-level final constant instead of method variable
[
https://issues.apache.org/jira/browse/HADOOP-11709?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14372798#comment-14372798
]
Hudson commented on HADOOP-11709:
-
FAILURE: Integrated in Hadoop-Hdfs-trunk-Java8 #130 (See
[https://builds.apache.org/job/Hadoop-Hdfs-trunk-Java8/130/])
HADOOP-11709. Time.NANOSECONDS_PER_MILLISECOND - use class-level final constant
instead of method variable. Contributed by Ajith S. (ozawa: rev
43dde502b3be2133d62f1f074f016f35a56a7e2c)
* hadoop-common-project/hadoop-common/CHANGES.txt
*
hadoop-common-project/hadoop-common/src/main/java/org/apache/hadoop/util/Time.java
> Time.NANOSECONDS_PER_MILLISECOND - use class-level final constant instead of
> method variable
> -
>
> Key: HADOOP-11709
> URL: https://issues.apache.org/jira/browse/HADOOP-11709
> Project: Hadoop Common
> Issue Type: Improvement
>Reporter: Ajith S
>Assignee: Ajith S
>Priority: Trivial
> Labels: beginner, newbie
> Fix For: 2.8.0
>
> Attachments: 001-HDFS-7919.patch
>
>
> NANOSECONDS_PER_MILLISECOND constant can be moved to class level instead of
> creating it in each method call.
> {code}
> org.apache.hadoop.util.Time.java
> public static long monotonicNow() {
> final long NANOSECONDS_PER_MILLISECOND = 100;
> return System.nanoTime() / NANOSECONDS_PER_MILLISECOND;
> }
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (HADOOP-11447) Add a more meaningful toString method to SampleStat and MutableStat
[ https://issues.apache.org/jira/browse/HADOOP-11447?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14372791#comment-14372791 ] Hudson commented on HADOOP-11447: - FAILURE: Integrated in Hadoop-Hdfs-trunk-Java8 #130 (See [https://builds.apache.org/job/Hadoop-Hdfs-trunk-Java8/130/]) HADOOP-11447. Add a more meaningful toString method to SampleStat and MutableStat. (kasha) (kasha: rev fe5c23b670c773145b87fecfaf9191536e9f1c51) * hadoop-common-project/hadoop-common/CHANGES.txt * hadoop-common-project/hadoop-common/src/main/java/org/apache/hadoop/metrics2/lib/MutableStat.java * hadoop-common-project/hadoop-common/src/main/java/org/apache/hadoop/metrics2/util/SampleStat.java > Add a more meaningful toString method to SampleStat and MutableStat > --- > > Key: HADOOP-11447 > URL: https://issues.apache.org/jira/browse/HADOOP-11447 > Project: Hadoop Common > Issue Type: Improvement > Components: metrics >Affects Versions: 2.6.0 >Reporter: Karthik Kambatla >Assignee: Karthik Kambatla >Priority: Minor > Fix For: 2.8.0 > > Attachments: hadoop-11447-1.patch, hadoop-11447-2.patch > > > SampleStat and MutableStat don't override the toString method. A more > meaningful implementation could help with debugging. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HADOOP-11709) Time.NANOSECONDS_PER_MILLISECOND - use class-level final constant instead of method variable
[
https://issues.apache.org/jira/browse/HADOOP-11709?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14372772#comment-14372772
]
Hudson commented on HADOOP-11709:
-
FAILURE: Integrated in Hadoop-Hdfs-trunk #2071 (See
[https://builds.apache.org/job/Hadoop-Hdfs-trunk/2071/])
HADOOP-11709. Time.NANOSECONDS_PER_MILLISECOND - use class-level final constant
instead of method variable. Contributed by Ajith S. (ozawa: rev
43dde502b3be2133d62f1f074f016f35a56a7e2c)
* hadoop-common-project/hadoop-common/CHANGES.txt
*
hadoop-common-project/hadoop-common/src/main/java/org/apache/hadoop/util/Time.java
> Time.NANOSECONDS_PER_MILLISECOND - use class-level final constant instead of
> method variable
> -
>
> Key: HADOOP-11709
> URL: https://issues.apache.org/jira/browse/HADOOP-11709
> Project: Hadoop Common
> Issue Type: Improvement
>Reporter: Ajith S
>Assignee: Ajith S
>Priority: Trivial
> Labels: beginner, newbie
> Fix For: 2.8.0
>
> Attachments: 001-HDFS-7919.patch
>
>
> NANOSECONDS_PER_MILLISECOND constant can be moved to class level instead of
> creating it in each method call.
> {code}
> org.apache.hadoop.util.Time.java
> public static long monotonicNow() {
> final long NANOSECONDS_PER_MILLISECOND = 100;
> return System.nanoTime() / NANOSECONDS_PER_MILLISECOND;
> }
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (HADOOP-11447) Add a more meaningful toString method to SampleStat and MutableStat
[ https://issues.apache.org/jira/browse/HADOOP-11447?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14372765#comment-14372765 ] Hudson commented on HADOOP-11447: - FAILURE: Integrated in Hadoop-Hdfs-trunk #2071 (See [https://builds.apache.org/job/Hadoop-Hdfs-trunk/2071/]) HADOOP-11447. Add a more meaningful toString method to SampleStat and MutableStat. (kasha) (kasha: rev fe5c23b670c773145b87fecfaf9191536e9f1c51) * hadoop-common-project/hadoop-common/src/main/java/org/apache/hadoop/metrics2/util/SampleStat.java * hadoop-common-project/hadoop-common/src/main/java/org/apache/hadoop/metrics2/lib/MutableStat.java * hadoop-common-project/hadoop-common/CHANGES.txt > Add a more meaningful toString method to SampleStat and MutableStat > --- > > Key: HADOOP-11447 > URL: https://issues.apache.org/jira/browse/HADOOP-11447 > Project: Hadoop Common > Issue Type: Improvement > Components: metrics >Affects Versions: 2.6.0 >Reporter: Karthik Kambatla >Assignee: Karthik Kambatla >Priority: Minor > Fix For: 2.8.0 > > Attachments: hadoop-11447-1.patch, hadoop-11447-2.patch > > > SampleStat and MutableStat don't override the toString method. A more > meaningful implementation could help with debugging. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HADOOP-11447) Add a more meaningful toString method to SampleStat and MutableStat
[ https://issues.apache.org/jira/browse/HADOOP-11447?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14372739#comment-14372739 ] Hudson commented on HADOOP-11447: - FAILURE: Integrated in Hadoop-Mapreduce-trunk #2089 (See [https://builds.apache.org/job/Hadoop-Mapreduce-trunk/2089/]) HADOOP-11447. Add a more meaningful toString method to SampleStat and MutableStat. (kasha) (kasha: rev fe5c23b670c773145b87fecfaf9191536e9f1c51) * hadoop-common-project/hadoop-common/src/main/java/org/apache/hadoop/metrics2/util/SampleStat.java * hadoop-common-project/hadoop-common/CHANGES.txt * hadoop-common-project/hadoop-common/src/main/java/org/apache/hadoop/metrics2/lib/MutableStat.java > Add a more meaningful toString method to SampleStat and MutableStat > --- > > Key: HADOOP-11447 > URL: https://issues.apache.org/jira/browse/HADOOP-11447 > Project: Hadoop Common > Issue Type: Improvement > Components: metrics >Affects Versions: 2.6.0 >Reporter: Karthik Kambatla >Assignee: Karthik Kambatla >Priority: Minor > Fix For: 2.8.0 > > Attachments: hadoop-11447-1.patch, hadoop-11447-2.patch > > > SampleStat and MutableStat don't override the toString method. A more > meaningful implementation could help with debugging. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HADOOP-11709) Time.NANOSECONDS_PER_MILLISECOND - use class-level final constant instead of method variable
[
https://issues.apache.org/jira/browse/HADOOP-11709?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14372746#comment-14372746
]
Hudson commented on HADOOP-11709:
-
FAILURE: Integrated in Hadoop-Mapreduce-trunk #2089 (See
[https://builds.apache.org/job/Hadoop-Mapreduce-trunk/2089/])
HADOOP-11709. Time.NANOSECONDS_PER_MILLISECOND - use class-level final constant
instead of method variable. Contributed by Ajith S. (ozawa: rev
43dde502b3be2133d62f1f074f016f35a56a7e2c)
* hadoop-common-project/hadoop-common/CHANGES.txt
*
hadoop-common-project/hadoop-common/src/main/java/org/apache/hadoop/util/Time.java
> Time.NANOSECONDS_PER_MILLISECOND - use class-level final constant instead of
> method variable
> -
>
> Key: HADOOP-11709
> URL: https://issues.apache.org/jira/browse/HADOOP-11709
> Project: Hadoop Common
> Issue Type: Improvement
>Reporter: Ajith S
>Assignee: Ajith S
>Priority: Trivial
> Labels: beginner, newbie
> Fix For: 2.8.0
>
> Attachments: 001-HDFS-7919.patch
>
>
> NANOSECONDS_PER_MILLISECOND constant can be moved to class level instead of
> creating it in each method call.
> {code}
> org.apache.hadoop.util.Time.java
> public static long monotonicNow() {
> final long NANOSECONDS_PER_MILLISECOND = 100;
> return System.nanoTime() / NANOSECONDS_PER_MILLISECOND;
> }
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (HADOOP-11447) Add a more meaningful toString method to SampleStat and MutableStat
[ https://issues.apache.org/jira/browse/HADOOP-11447?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14372660#comment-14372660 ] Hudson commented on HADOOP-11447: - FAILURE: Integrated in Hadoop-Yarn-trunk #873 (See [https://builds.apache.org/job/Hadoop-Yarn-trunk/873/]) HADOOP-11447. Add a more meaningful toString method to SampleStat and MutableStat. (kasha) (kasha: rev fe5c23b670c773145b87fecfaf9191536e9f1c51) * hadoop-common-project/hadoop-common/CHANGES.txt * hadoop-common-project/hadoop-common/src/main/java/org/apache/hadoop/metrics2/lib/MutableStat.java * hadoop-common-project/hadoop-common/src/main/java/org/apache/hadoop/metrics2/util/SampleStat.java > Add a more meaningful toString method to SampleStat and MutableStat > --- > > Key: HADOOP-11447 > URL: https://issues.apache.org/jira/browse/HADOOP-11447 > Project: Hadoop Common > Issue Type: Improvement > Components: metrics >Affects Versions: 2.6.0 >Reporter: Karthik Kambatla >Assignee: Karthik Kambatla >Priority: Minor > Fix For: 2.8.0 > > Attachments: hadoop-11447-1.patch, hadoop-11447-2.patch > > > SampleStat and MutableStat don't override the toString method. A more > meaningful implementation could help with debugging. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HADOOP-11709) Time.NANOSECONDS_PER_MILLISECOND - use class-level final constant instead of method variable
[
https://issues.apache.org/jira/browse/HADOOP-11709?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14372667#comment-14372667
]
Hudson commented on HADOOP-11709:
-
FAILURE: Integrated in Hadoop-Yarn-trunk #873 (See
[https://builds.apache.org/job/Hadoop-Yarn-trunk/873/])
HADOOP-11709. Time.NANOSECONDS_PER_MILLISECOND - use class-level final constant
instead of method variable. Contributed by Ajith S. (ozawa: rev
43dde502b3be2133d62f1f074f016f35a56a7e2c)
* hadoop-common-project/hadoop-common/CHANGES.txt
*
hadoop-common-project/hadoop-common/src/main/java/org/apache/hadoop/util/Time.java
> Time.NANOSECONDS_PER_MILLISECOND - use class-level final constant instead of
> method variable
> -
>
> Key: HADOOP-11709
> URL: https://issues.apache.org/jira/browse/HADOOP-11709
> Project: Hadoop Common
> Issue Type: Improvement
>Reporter: Ajith S
>Assignee: Ajith S
>Priority: Trivial
> Labels: beginner, newbie
> Fix For: 2.8.0
>
> Attachments: 001-HDFS-7919.patch
>
>
> NANOSECONDS_PER_MILLISECOND constant can be moved to class level instead of
> creating it in each method call.
> {code}
> org.apache.hadoop.util.Time.java
> public static long monotonicNow() {
> final long NANOSECONDS_PER_MILLISECOND = 100;
> return System.nanoTime() / NANOSECONDS_PER_MILLISECOND;
> }
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (HADOOP-11709) Time.NANOSECONDS_PER_MILLISECOND - use class-level final constant instead of method variable
[
https://issues.apache.org/jira/browse/HADOOP-11709?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14372653#comment-14372653
]
Hudson commented on HADOOP-11709:
-
FAILURE: Integrated in Hadoop-Yarn-trunk-Java8 #139 (See
[https://builds.apache.org/job/Hadoop-Yarn-trunk-Java8/139/])
HADOOP-11709. Time.NANOSECONDS_PER_MILLISECOND - use class-level final constant
instead of method variable. Contributed by Ajith S. (ozawa: rev
43dde502b3be2133d62f1f074f016f35a56a7e2c)
*
hadoop-common-project/hadoop-common/src/main/java/org/apache/hadoop/util/Time.java
* hadoop-common-project/hadoop-common/CHANGES.txt
> Time.NANOSECONDS_PER_MILLISECOND - use class-level final constant instead of
> method variable
> -
>
> Key: HADOOP-11709
> URL: https://issues.apache.org/jira/browse/HADOOP-11709
> Project: Hadoop Common
> Issue Type: Improvement
>Reporter: Ajith S
>Assignee: Ajith S
>Priority: Trivial
> Labels: beginner, newbie
> Fix For: 2.8.0
>
> Attachments: 001-HDFS-7919.patch
>
>
> NANOSECONDS_PER_MILLISECOND constant can be moved to class level instead of
> creating it in each method call.
> {code}
> org.apache.hadoop.util.Time.java
> public static long monotonicNow() {
> final long NANOSECONDS_PER_MILLISECOND = 100;
> return System.nanoTime() / NANOSECONDS_PER_MILLISECOND;
> }
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (HADOOP-11447) Add a more meaningful toString method to SampleStat and MutableStat
[ https://issues.apache.org/jira/browse/HADOOP-11447?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14372646#comment-14372646 ] Hudson commented on HADOOP-11447: - FAILURE: Integrated in Hadoop-Yarn-trunk-Java8 #139 (See [https://builds.apache.org/job/Hadoop-Yarn-trunk-Java8/139/]) HADOOP-11447. Add a more meaningful toString method to SampleStat and MutableStat. (kasha) (kasha: rev fe5c23b670c773145b87fecfaf9191536e9f1c51) * hadoop-common-project/hadoop-common/src/main/java/org/apache/hadoop/metrics2/lib/MutableStat.java * hadoop-common-project/hadoop-common/CHANGES.txt * hadoop-common-project/hadoop-common/src/main/java/org/apache/hadoop/metrics2/util/SampleStat.java > Add a more meaningful toString method to SampleStat and MutableStat > --- > > Key: HADOOP-11447 > URL: https://issues.apache.org/jira/browse/HADOOP-11447 > Project: Hadoop Common > Issue Type: Improvement > Components: metrics >Affects Versions: 2.6.0 >Reporter: Karthik Kambatla >Assignee: Karthik Kambatla >Priority: Minor > Fix For: 2.8.0 > > Attachments: hadoop-11447-1.patch, hadoop-11447-2.patch > > > SampleStat and MutableStat don't override the toString method. A more > meaningful implementation could help with debugging. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
