[jira] [Updated] (MAPREDUCE-5657) [JDK8] Fix Javadoc errors caused by incorrect or illegal tags in doc comments
[ https://issues.apache.org/jira/browse/MAPREDUCE-5657?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tsuyoshi Ozawa updated MAPREDUCE-5657: -- Attachment: RandomWriter.png [~ajisakaa] thank you for updating a patch. I checked RandomWriter's page, but layout looks broken. Attaching RandomWriter.html's png. Could you check such pages? This should be like this: https://hadoop.apache.org/docs/r1.2.1/api/org/apache/hadoop/examples/RandomWriter.html > [JDK8] Fix Javadoc errors caused by incorrect or illegal tags in doc comments > - > > Key: MAPREDUCE-5657 > URL: https://issues.apache.org/jira/browse/MAPREDUCE-5657 > Project: Hadoop Map/Reduce > Issue Type: Bug > Components: documentation >Affects Versions: 2.7.0 >Reporter: Andrew Purtell >Assignee: Akira AJISAKA >Priority: Minor > Attachments: 5657-branch-2.patch, 5657-branch-2.patch, > 5657-trunk.patch, 5657-trunk.patch, MAPREDUCE-5657-002.patch, > MAPREDUCE-5657-003.patch, MAPREDUCE-5657-wip3.patch, RandomWriter.png, > build.log > > > Javadoc is more strict by default in JDK8 and will error out on malformed or > illegal tags found in doc comments. Although tagged as JDK8 all of the > required changes are generic Javadoc cleanups. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (MAPREDUCE-5657) [JDK8] Fix Javadoc errors caused by incorrect or illegal tags in doc comments
[
https://issues.apache.org/jira/browse/MAPREDUCE-5657?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14342923#comment-14342923
]
Hadoop QA commented on MAPREDUCE-5657:
--
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12701824/RandomWriter.png
against trunk revision 67ed593.
{color:red}-1 patch{color}. The patch command could not apply the patch.
Console output:
https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/5236//console
This message is automatically generated.
> [JDK8] Fix Javadoc errors caused by incorrect or illegal tags in doc comments
> -
>
> Key: MAPREDUCE-5657
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-5657
> Project: Hadoop Map/Reduce
> Issue Type: Bug
> Components: documentation
>Affects Versions: 2.7.0
>Reporter: Andrew Purtell
>Assignee: Akira AJISAKA
>Priority: Minor
> Attachments: 5657-branch-2.patch, 5657-branch-2.patch,
> 5657-trunk.patch, 5657-trunk.patch, MAPREDUCE-5657-002.patch,
> MAPREDUCE-5657-003.patch, MAPREDUCE-5657-wip3.patch, RandomWriter.png,
> build.log
>
>
> Javadoc is more strict by default in JDK8 and will error out on malformed or
> illegal tags found in doc comments. Although tagged as JDK8 all of the
> required changes are generic Javadoc cleanups.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (MAPREDUCE-5657) [JDK8] Fix Javadoc errors caused by incorrect or illegal tags in doc comments
[ https://issues.apache.org/jira/browse/MAPREDUCE-5657?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Akira AJISAKA updated MAPREDUCE-5657: - Attachment: MAPREDUCE-5657-004.patch Thanks [~ozawa] for the review comment! Updated the patch. > [JDK8] Fix Javadoc errors caused by incorrect or illegal tags in doc comments > - > > Key: MAPREDUCE-5657 > URL: https://issues.apache.org/jira/browse/MAPREDUCE-5657 > Project: Hadoop Map/Reduce > Issue Type: Bug > Components: documentation >Affects Versions: 2.7.0 >Reporter: Andrew Purtell >Assignee: Akira AJISAKA >Priority: Minor > Attachments: 5657-branch-2.patch, 5657-branch-2.patch, > 5657-trunk.patch, 5657-trunk.patch, MAPREDUCE-5657-002.patch, > MAPREDUCE-5657-003.patch, MAPREDUCE-5657-004.patch, > MAPREDUCE-5657-wip3.patch, RandomWriter.png, build.log > > > Javadoc is more strict by default in JDK8 and will error out on malformed or > illegal tags found in doc comments. Although tagged as JDK8 all of the > required changes are generic Javadoc cleanups. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (MAPREDUCE-6096) SummarizedJob class NPEs with some jhist files
[
https://issues.apache.org/jira/browse/MAPREDUCE-6096?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14343001#comment-14343001
]
Hadoop QA commented on MAPREDUCE-6096:
--
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12701803/MAPREDUCE-6096-v7.patch
against trunk revision dd9cd07.
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 7 new
or modified test files.
{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 2
release audit warnings.
{color:red}-1 core tests{color}. The patch failed these unit tests in
hadoop-common-project/hadoop-auth hadoop-common-project/hadoop-common
hadoop-hdfs-project/hadoop-hdfs
hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-core
hadoop-tools/hadoop-distcp:
org.apache.hadoop.security.token.delegation.web.TestWebDelegationToken
Test results:
https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/5235//testReport/
Release audit warnings:
https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/5235//artifact/patchprocess/patchReleaseAuditProblems.txt
Console output:
https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/5235//console
This message is automatically generated.
> SummarizedJob class NPEs with some jhist files
> --
>
> Key: MAPREDUCE-6096
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-6096
> Project: Hadoop Map/Reduce
> Issue Type: Bug
> Components: jobhistoryserver
>Affects Versions: trunk
>Reporter: zhangyubiao
> Labels: easyfix, patch
> Attachments: MAPREDUCE-6096-v2.patch, MAPREDUCE-6096-v3.patch,
> MAPREDUCE-6096-v4.patch, MAPREDUCE-6096-v5.patch, MAPREDUCE-6096-v6.patch,
> MAPREDUCE-6096-v7.patch, MAPREDUCE-6096.patch,
> job_1410427642147_0124-1411726671220-hadp-word+count-1411726696863-1-1-SUCCEEDED-default.jhist
>
>
> When I Parse the JobHistory in the HistoryFile,I use the Hadoop System's
> map-reduce-client-core project
> org.apache.hadoop.mapreduce.jobhistory.JobHistoryParser class and
> HistoryViewer$SummarizedJob to Parse the JobHistoryFile(Just Like
> job_1408862281971_489761-1410883171851_XXX.jhist)
> and it throw an Exception Just Like
> Exception in thread "pool-1-thread-1" java.lang.NullPointerException
> at
> org.apache.hadoop.mapreduce.jobhistory.HistoryViewer$SummarizedJob.(HistoryViewer.java:626)
> at
> com.jd.hadoop.log.parse.ParseLogService.getJobDetail(ParseLogService.java:70)
> After I'm see the SummarizedJob class I find that attempt.getTaskStatus() is
> NULL ， So I change the order of
> attempt.getTaskStatus().equals (TaskStatus.State.FAILED.toString()) to
> TaskStatus.State.FAILED.toString().equals(attempt.getTaskStatus())
> and it works well .
> So I wonder If we can change all attempt.getTaskStatus() after
> TaskStatus.State.XXX.toString() ?
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (MAPREDUCE-5657) [JDK8] Fix Javadoc errors caused by incorrect or illegal tags in doc comments
[
https://issues.apache.org/jira/browse/MAPREDUCE-5657?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14343094#comment-14343094
]
Hadoop QA commented on MAPREDUCE-5657:
--
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12701828/MAPREDUCE-5657-004.patch
against trunk revision 67ed593.
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 1 new
or modified test files.
{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-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-app
hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-common
hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-core
hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-jobclient
hadoop-mapreduce-project/hadoop-mapreduce-examples hadoop-tools/hadoop-distcp
hadoop-tools/hadoop-extras hadoop-tools/hadoop-gridmix
hadoop-tools/hadoop-openstack hadoop-tools/hadoop-rumen.
Test results:
https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/5237//testReport/
Console output:
https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/5237//console
This message is automatically generated.
> [JDK8] Fix Javadoc errors caused by incorrect or illegal tags in doc comments
> -
>
> Key: MAPREDUCE-5657
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-5657
> Project: Hadoop Map/Reduce
> Issue Type: Bug
> Components: documentation
>Affects Versions: 2.7.0
>Reporter: Andrew Purtell
>Assignee: Akira AJISAKA
>Priority: Minor
> Attachments: 5657-branch-2.patch, 5657-branch-2.patch,
> 5657-trunk.patch, 5657-trunk.patch, MAPREDUCE-5657-002.patch,
> MAPREDUCE-5657-003.patch, MAPREDUCE-5657-004.patch,
> MAPREDUCE-5657-wip3.patch, RandomWriter.png, build.log
>
>
> Javadoc is more strict by default in JDK8 and will error out on malformed or
> illegal tags found in doc comments. Although tagged as JDK8 all of the
> required changes are generic Javadoc cleanups.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (MAPREDUCE-5854) Move the search box in UI from the right side to the left side
[ https://issues.apache.org/jira/browse/MAPREDUCE-5854?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chang Li updated MAPREDUCE-5854: Assignee: (was: Chang Li) > Move the search box in UI from the right side to the left side > -- > > Key: MAPREDUCE-5854 > URL: https://issues.apache.org/jira/browse/MAPREDUCE-5854 > Project: Hadoop Map/Reduce > Issue Type: Improvement >Affects Versions: 0.23.9 >Reporter: Jinhui Liu > Attachments: MAPREDUCE-5854.patch, MAPREDUCE-5854.patch > > > In the UI for resoure manager, job history, and job configuration (this might > not be a complete list), there is a search box at the top-right corner of the > listed content. This search box is frequently used but it is usually not > visible due to right-alignment. Extra scroll is needed to make it visable and > it is not convenient. It would be good to move it to the left-side, next to > the "Show ... Entries" drop-down box. > In the same spirit, the "First|Preious|...|Next|Last" at the bottom-right > corner of the listed content can also be moved to the left side. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (MAPREDUCE-5854) Move the search box in UI from the right side to the left side
[
https://issues.apache.org/jira/browse/MAPREDUCE-5854?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14343335#comment-14343335
]
Hadoop QA commented on MAPREDUCE-5854:
--
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12652014/MAPREDUCE-5854.patch
against trunk revision ca1c00b.
{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-yarn-project/hadoop-yarn/hadoop-yarn-common.
Test results:
https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/5238//testReport/
Console output:
https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/5238//console
This message is automatically generated.
> Move the search box in UI from the right side to the left side
> --
>
> Key: MAPREDUCE-5854
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-5854
> Project: Hadoop Map/Reduce
> Issue Type: Improvement
>Affects Versions: 0.23.9
>Reporter: Jinhui Liu
> Attachments: MAPREDUCE-5854.patch, MAPREDUCE-5854.patch
>
>
> In the UI for resoure manager, job history, and job configuration (this might
> not be a complete list), there is a search box at the top-right corner of the
> listed content. This search box is frequently used but it is usually not
> visible due to right-alignment. Extra scroll is needed to make it visable and
> it is not convenient. It would be good to move it to the left-side, next to
> the "Show ... Entries" drop-down box.
> In the same spirit, the "First|Preious|...|Next|Last" at the bottom-right
> corner of the listed content can also be moved to the left side.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (MAPREDUCE-5583) Ability to limit running map and reduce tasks
[ https://issues.apache.org/jira/browse/MAPREDUCE-5583?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14343756#comment-14343756 ] Jason Lowe commented on MAPREDUCE-5583: --- bq. So the return value for requestLimits.put(newReqLimit, newReqLimit) can always be null or the same as newReqLimit (event in numOfContainers), so checking for "oldReqLimit.getNumContainers() < limit" sounds unnecessary to me. The return value from requestLimits.put will be the previously stored value requested limit which is not necessarily newReqLimit if it's not null. If a job with 3 tasks has a limit of 1 task and 1 is already running then the current ask is 0. As that task completes the ask will go from 0 to 1 since we can now run another task. In that case oldReqLimit.getNumContainers == 0 and newReqLimit.getNumContainers() == 1, so they are not the same. The intent of this check is to re-send the ask if the limit is being raised. If we don't re-send the ask when the limit goes up then the RM may fail to allocate more containers when we need them which would result in a hang. (AM thinks it's asking, RM thinks the AM doesn't want any.) > Ability to limit running map and reduce tasks > - > > Key: MAPREDUCE-5583 > URL: https://issues.apache.org/jira/browse/MAPREDUCE-5583 > Project: Hadoop Map/Reduce > Issue Type: Improvement > Components: mr-am, mrv2 >Affects Versions: 0.23.9, 2.1.1-beta >Reporter: Jason Lowe >Assignee: Jason Lowe > Attachments: MAPREDUCE-5583-branch2.4.1.patch, > MAPREDUCE-5583v1.patch, MAPREDUCE-5583v2.patch, MAPREDUCE-5583v3.patch, > MAPREDUCE-5583v4.patch > > > It would be nice if users could specify a limit to the number of map or > reduce tasks that are running simultaneously. Occasionally users are > performing operations in tasks that can lead to DDoS scenarios if too many > tasks run simultaneously (e.g.: accessing a database, web service, etc.). > Having the ability to throttle the number of tasks simultaneously running > would provide users a way to mitigate issues with too many tasks on a large > cluster attempting to access a serivce at any one time. > This is similar to the functionality requested by MAPREDUCE-224 and > implemented by HADOOP-3412 but was dropped in mrv2. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (MAPREDUCE-6260) Convert site documentation to markdown
[ https://issues.apache.org/jira/browse/MAPREDUCE-6260?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14343969#comment-14343969 ] Masatake Iwasaki commented on MAPREDUCE-6260: - I submitted the backport patch in HADOOP-11633. > Convert site documentation to markdown > -- > > Key: MAPREDUCE-6260 > URL: https://issues.apache.org/jira/browse/MAPREDUCE-6260 > Project: Hadoop Map/Reduce > Issue Type: Improvement > Components: documentation >Affects Versions: 3.0.0 >Reporter: Allen Wittenauer >Assignee: Masatake Iwasaki > Fix For: 3.0.0 > > Attachments: MAPREDUCE-6260-00.patch, MAPREDUCE-6260-01.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (MAPREDUCE-5583) Ability to limit running map and reduce tasks
[ https://issues.apache.org/jira/browse/MAPREDUCE-5583?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14344331#comment-14344331 ] Junping Du commented on MAPREDUCE-5583: --- bq. As that task completes the ask will go from 0 to 1 since we can now run another task. In that case oldReqLimit.getNumContainers == 0 and newReqLimit.getNumContainers() == 1, so they are not the same. I see. I always forgot our old hacking that compare() in ResourceRequestComparator is inconsistent with equals() in ResourceRequest. :( Latest patch LGTM. Given latest patch is upload almost 1 week ago, kick off Jenkins test again. +1 pending on Jenkins result. > Ability to limit running map and reduce tasks > - > > Key: MAPREDUCE-5583 > URL: https://issues.apache.org/jira/browse/MAPREDUCE-5583 > Project: Hadoop Map/Reduce > Issue Type: Improvement > Components: mr-am, mrv2 >Affects Versions: 0.23.9, 2.1.1-beta >Reporter: Jason Lowe >Assignee: Jason Lowe > Attachments: MAPREDUCE-5583-branch2.4.1.patch, > MAPREDUCE-5583v1.patch, MAPREDUCE-5583v2.patch, MAPREDUCE-5583v3.patch, > MAPREDUCE-5583v4.patch > > > It would be nice if users could specify a limit to the number of map or > reduce tasks that are running simultaneously. Occasionally users are > performing operations in tasks that can lead to DDoS scenarios if too many > tasks run simultaneously (e.g.: accessing a database, web service, etc.). > Having the ability to throttle the number of tasks simultaneously running > would provide users a way to mitigate issues with too many tasks on a large > cluster attempting to access a serivce at any one time. > This is similar to the functionality requested by MAPREDUCE-224 and > implemented by HADOOP-3412 but was dropped in mrv2. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (MAPREDUCE-5583) Ability to limit running map and reduce tasks
[
https://issues.apache.org/jira/browse/MAPREDUCE-5583?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14344431#comment-14344431
]
Hadoop QA commented on MAPREDUCE-5583:
--
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12700591/MAPREDUCE-5583v4.patch
against trunk revision b18d383.
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 1 new
or modified test files.
{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-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-app
hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-core.
Test results:
https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/5239//testReport/
Console output:
https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/5239//console
This message is automatically generated.
> Ability to limit running map and reduce tasks
> -
>
> Key: MAPREDUCE-5583
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-5583
> Project: Hadoop Map/Reduce
> Issue Type: Improvement
> Components: mr-am, mrv2
>Affects Versions: 0.23.9, 2.1.1-beta
>Reporter: Jason Lowe
>Assignee: Jason Lowe
> Attachments: MAPREDUCE-5583-branch2.4.1.patch,
> MAPREDUCE-5583v1.patch, MAPREDUCE-5583v2.patch, MAPREDUCE-5583v3.patch,
> MAPREDUCE-5583v4.patch
>
>
> It would be nice if users could specify a limit to the number of map or
> reduce tasks that are running simultaneously. Occasionally users are
> performing operations in tasks that can lead to DDoS scenarios if too many
> tasks run simultaneously (e.g.: accessing a database, web service, etc.).
> Having the ability to throttle the number of tasks simultaneously running
> would provide users a way to mitigate issues with too many tasks on a large
> cluster attempting to access a serivce at any one time.
> This is similar to the functionality requested by MAPREDUCE-224 and
> implemented by HADOOP-3412 but was dropped in mrv2.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (MAPREDUCE-5657) [JDK8] Fix Javadoc errors caused by incorrect or illegal tags in doc comments
[ https://issues.apache.org/jira/browse/MAPREDUCE-5657?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tsuyoshi Ozawa updated MAPREDUCE-5657: -- Attachment: randomtextwriter.png Please fix RandomTextWriter also. > [JDK8] Fix Javadoc errors caused by incorrect or illegal tags in doc comments > - > > Key: MAPREDUCE-5657 > URL: https://issues.apache.org/jira/browse/MAPREDUCE-5657 > Project: Hadoop Map/Reduce > Issue Type: Bug > Components: documentation >Affects Versions: 2.7.0 >Reporter: Andrew Purtell >Assignee: Akira AJISAKA >Priority: Minor > Attachments: 5657-branch-2.patch, 5657-branch-2.patch, > 5657-trunk.patch, 5657-trunk.patch, MAPREDUCE-5657-002.patch, > MAPREDUCE-5657-003.patch, MAPREDUCE-5657-004.patch, > MAPREDUCE-5657-wip3.patch, RandomWriter.png, build.log, randomtextwriter.png > > > Javadoc is more strict by default in JDK8 and will error out on malformed or > illegal tags found in doc comments. Although tagged as JDK8 all of the > required changes are generic Javadoc cleanups. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (MAPREDUCE-5657) [JDK8] Fix Javadoc errors caused by incorrect or illegal tags in doc comments
[ https://issues.apache.org/jira/browse/MAPREDUCE-5657?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tsuyoshi Ozawa updated MAPREDUCE-5657: -- Status: Open (was: Patch Available) > [JDK8] Fix Javadoc errors caused by incorrect or illegal tags in doc comments > - > > Key: MAPREDUCE-5657 > URL: https://issues.apache.org/jira/browse/MAPREDUCE-5657 > Project: Hadoop Map/Reduce > Issue Type: Bug > Components: documentation >Affects Versions: 2.7.0 >Reporter: Andrew Purtell >Assignee: Akira AJISAKA >Priority: Minor > Attachments: 5657-branch-2.patch, 5657-branch-2.patch, > 5657-trunk.patch, 5657-trunk.patch, MAPREDUCE-5657-002.patch, > MAPREDUCE-5657-003.patch, MAPREDUCE-5657-004.patch, > MAPREDUCE-5657-wip3.patch, RandomWriter.png, build.log, randomtextwriter.png > > > Javadoc is more strict by default in JDK8 and will error out on malformed or > illegal tags found in doc comments. Although tagged as JDK8 all of the > required changes are generic Javadoc cleanups. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (MAPREDUCE-6268) Task Attempt API's URL is typo
Ryu Kobayashi created MAPREDUCE-6268: Summary: Task Attempt API's URL is typo Key: MAPREDUCE-6268 URL: https://issues.apache.org/jira/browse/MAPREDUCE-6268 Project: Hadoop Map/Reduce Issue Type: Bug Reporter: Ryu Kobayashi Priority: Minor Task Attempt API's URL is typo. attempt is wrong -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (MAPREDUCE-6268) Task Attempt API's URL is typo
[ https://issues.apache.org/jira/browse/MAPREDUCE-6268?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ryu Kobayashi updated MAPREDUCE-6268: - Attachment: MAPREDUCE-6268.patch > Task Attempt API's URL is typo > -- > > Key: MAPREDUCE-6268 > URL: https://issues.apache.org/jira/browse/MAPREDUCE-6268 > Project: Hadoop Map/Reduce > Issue Type: Bug >Reporter: Ryu Kobayashi >Priority: Minor > Attachments: MAPREDUCE-6268.patch > > > Task Attempt API's URL is typo. attempt is wrong -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (MAPREDUCE-6268) Task Attempt API's URL is typo
[
https://issues.apache.org/jira/browse/MAPREDUCE-6268?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14344658#comment-14344658
]
Tsuyoshi Ozawa commented on MAPREDUCE-6268:
---
Good catch. I checked HsWebServices:
{code}
@Path("/mapreduce/jobs/{jobid}/tasks/{taskid}/attempts/{attemptid}")
{code}
+1, committing this shortly.
> Task Attempt API's URL is typo
> --
>
> Key: MAPREDUCE-6268
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-6268
> Project: Hadoop Map/Reduce
> Issue Type: Bug
>Reporter: Ryu Kobayashi
>Priority: Minor
> Attachments: MAPREDUCE-6268.patch
>
>
> Task Attempt API's URL is typo. attempt is wrong
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (MAPREDUCE-6268) Fix typo in Task Attempt API's URL
[ https://issues.apache.org/jira/browse/MAPREDUCE-6268?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tsuyoshi Ozawa updated MAPREDUCE-6268: -- Summary: Fix typo in Task Attempt API's URL (was: Task Attempt API's URL is typo) > Fix typo in Task Attempt API's URL > -- > > Key: MAPREDUCE-6268 > URL: https://issues.apache.org/jira/browse/MAPREDUCE-6268 > Project: Hadoop Map/Reduce > Issue Type: Bug >Reporter: Ryu Kobayashi >Priority: Minor > Attachments: MAPREDUCE-6268.patch > > > Task Attempt API's URL is typo. attempt is wrong -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (MAPREDUCE-6268) Fix typo in Task Attempt API's URL
[ https://issues.apache.org/jira/browse/MAPREDUCE-6268?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tsuyoshi Ozawa resolved MAPREDUCE-6268. --- Resolution: Fixed Fix Version/s: 2.7.0 Target Version/s: 2.7.0 Hadoop Flags: Reviewed > Fix typo in Task Attempt API's URL > -- > > Key: MAPREDUCE-6268 > URL: https://issues.apache.org/jira/browse/MAPREDUCE-6268 > Project: Hadoop Map/Reduce > Issue Type: Bug >Reporter: Ryu Kobayashi >Priority: Minor > Fix For: 2.7.0 > > Attachments: MAPREDUCE-6268.patch > > > Task Attempt API's URL is typo. attempt is wrong -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (MAPREDUCE-6268) Fix typo in Task Attempt API's URL
[ https://issues.apache.org/jira/browse/MAPREDUCE-6268?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14344672#comment-14344672 ] Tsuyoshi Ozawa commented on MAPREDUCE-6268: --- We don't need to wait CI since it's document issue. Committed this to trunk and branch-2. Thanks [~ryu_kobayashi] for your contribution! > Fix typo in Task Attempt API's URL > -- > > Key: MAPREDUCE-6268 > URL: https://issues.apache.org/jira/browse/MAPREDUCE-6268 > Project: Hadoop Map/Reduce > Issue Type: Bug >Reporter: Ryu Kobayashi >Priority: Minor > Fix For: 2.7.0 > > Attachments: MAPREDUCE-6268.patch > > > Task Attempt API's URL is typo. attempt is wrong -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (MAPREDUCE-6268) Fix typo in Task Attempt API's URL
[ https://issues.apache.org/jira/browse/MAPREDUCE-6268?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14344682#comment-14344682 ] Hudson commented on MAPREDUCE-6268: --- FAILURE: Integrated in Hadoop-trunk-Commit #7243 (See [https://builds.apache.org/job/Hadoop-trunk-Commit/7243/]) MAPREDUCE-6268. Fix typo in Task Attempt API's URL. Contributed by Ryu Kobayashi. (ozawa: rev 742f9d90c00f823ad7fea7e79702fcf238fa5721) * hadoop-mapreduce-project/CHANGES.txt * hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-hs/src/site/markdown/HistoryServerRest.md > Fix typo in Task Attempt API's URL > -- > > Key: MAPREDUCE-6268 > URL: https://issues.apache.org/jira/browse/MAPREDUCE-6268 > Project: Hadoop Map/Reduce > Issue Type: Bug >Reporter: Ryu Kobayashi >Priority: Minor > Fix For: 2.7.0 > > Attachments: MAPREDUCE-6268.patch > > > Task Attempt API's URL is typo. attempt is wrong -- This message was sent by Atlassian JIRA (v6.3.4#6332)
