[jira] [Commented] (HADOOP-7851) Configuration.getClasses() never returns the default value.
[ https://issues.apache.org/jira/browse/HADOOP-7851?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13156989#comment-13156989 ] Uma Maheswara Rao G commented on HADOOP-7851: - Yes Amar, My first pacth should adderss your comment. But i used directly StringUtils api directly. So, that i could avaoid two times get invokation. But coming to harsh comment, i thought to raise your point. But i could'nt find any usecase for setting "" for classnames. Do we have some use cases? If so, we can prefer 1st patch itself. Thanks Uma > Configuration.getClasses() never returns the default value. > --- > > Key: HADOOP-7851 > URL: https://issues.apache.org/jira/browse/HADOOP-7851 > Project: Hadoop Common > Issue Type: Bug > Components: conf >Affects Versions: 0.23.0 >Reporter: Amar Kamat >Assignee: Uma Maheswara Rao G > Labels: configuration > Fix For: 0.24.0, 0.23.1 > > Attachments: HADOOP-7851.patch, HADOOP-7851.patch > > > Configuration.getClasses() never returns the default value. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HADOOP-7851) Configuration.getClasses() never returns the default value.
[ https://issues.apache.org/jira/browse/HADOOP-7851?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13156984#comment-13156984 ] Amar Kamat commented on HADOOP-7851: Not setting a value for a configuration parameter is different from setting it to "". Hence when the parameter is not set, the default value should be returned. When the parameter is set (including "") then the specified value should be returned and not the default. Hence a simple check before invoking getTrimmedStrings() should suffice. > Configuration.getClasses() never returns the default value. > --- > > Key: HADOOP-7851 > URL: https://issues.apache.org/jira/browse/HADOOP-7851 > Project: Hadoop Common > Issue Type: Bug > Components: conf >Affects Versions: 0.23.0 >Reporter: Amar Kamat >Assignee: Uma Maheswara Rao G > Labels: configuration > Fix For: 0.24.0, 0.23.1 > > Attachments: HADOOP-7851.patch, HADOOP-7851.patch > > > Configuration.getClasses() never returns the default value. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HADOOP-1381) The distance between sync blocks in SequenceFiles should be configurable rather than hard coded to 2000 bytes
[ https://issues.apache.org/jira/browse/HADOOP-1381?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13156954#comment-13156954 ] Harsh J commented on HADOOP-1381: - Yes, it would end up writing a marker after each record, as sync-writing condition is checked after every record append. > The distance between sync blocks in SequenceFiles should be configurable > rather than hard coded to 2000 bytes > - > > Key: HADOOP-1381 > URL: https://issues.apache.org/jira/browse/HADOOP-1381 > Project: Hadoop Common > Issue Type: Improvement > Components: io >Affects Versions: 0.22.0 >Reporter: Owen O'Malley >Assignee: Harsh J > Fix For: 0.24.0 > > Attachments: HADOOP-1381.r1.diff, HADOOP-1381.r2.diff, > HADOOP-1381.r3.diff, HADOOP-1381.r4.diff > > > Currently SequenceFiles put in sync blocks every 2000 bytes. It would be much > better if it was configurable with a much higher default (1mb or so?). -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HADOOP-7861) changes2html.pl should generate links to HADOOP, HDFS, and MAPREDUCE jiras
[ https://issues.apache.org/jira/browse/HADOOP-7861?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13156951#comment-13156951 ] Hudson commented on HADOOP-7861: Integrated in Hadoop-Mapreduce-22-branch #92 (See [https://builds.apache.org/job/Hadoop-Mapreduce-22-branch/92/]) HADOOP-7861. changes2html.pl generates links to HADOOP, HDFS, and MAPREDUCE jiras. Contributed by Konstantin Shvachko. shv : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1205989 Files : * /hadoop/common/branches/branch-0.22/common/CHANGES.txt * /hadoop/common/branches/branch-0.22/common/src/docs/changes/changes2html.pl * /hadoop/common/branches/branch-0.22/hdfs/src/docs/changes/changes2html.pl * /hadoop/common/branches/branch-0.22/mapreduce/src/docs/changes/changes2html.pl > changes2html.pl should generate links to HADOOP, HDFS, and MAPREDUCE jiras > -- > > Key: HADOOP-7861 > URL: https://issues.apache.org/jira/browse/HADOOP-7861 > Project: Hadoop Common > Issue Type: Improvement > Components: documentation >Affects Versions: 0.20.0 >Reporter: Konstantin Shvachko >Assignee: Konstantin Shvachko > Fix For: 0.22.0 > > Attachments: changes2html.patch > > > changes2html.pl correctly generates links to HADOOP jiras only. This hasn't > been updated since projects split. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HADOOP-7861) changes2html.pl should generate links to HADOOP, HDFS, and MAPREDUCE jiras
[ https://issues.apache.org/jira/browse/HADOOP-7861?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13156941#comment-13156941 ] Hudson commented on HADOOP-7861: Integrated in Hadoop-Hdfs-22-branch #114 (See [https://builds.apache.org/job/Hadoop-Hdfs-22-branch/114/]) HADOOP-7861. changes2html.pl generates links to HADOOP, HDFS, and MAPREDUCE jiras. Contributed by Konstantin Shvachko. shv : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1205989 Files : * /hadoop/common/branches/branch-0.22/common/CHANGES.txt * /hadoop/common/branches/branch-0.22/common/src/docs/changes/changes2html.pl * /hadoop/common/branches/branch-0.22/hdfs/src/docs/changes/changes2html.pl * /hadoop/common/branches/branch-0.22/mapreduce/src/docs/changes/changes2html.pl > changes2html.pl should generate links to HADOOP, HDFS, and MAPREDUCE jiras > -- > > Key: HADOOP-7861 > URL: https://issues.apache.org/jira/browse/HADOOP-7861 > Project: Hadoop Common > Issue Type: Improvement > Components: documentation >Affects Versions: 0.20.0 >Reporter: Konstantin Shvachko >Assignee: Konstantin Shvachko > Fix For: 0.22.0 > > Attachments: changes2html.patch > > > changes2html.pl correctly generates links to HADOOP jiras only. This hasn't > been updated since projects split. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HADOOP-7861) changes2html.pl should generate links to HADOOP, HDFS, and MAPREDUCE jiras
[ https://issues.apache.org/jira/browse/HADOOP-7861?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13156916#comment-13156916 ] Hudson commented on HADOOP-7861: Integrated in Hadoop-Mapreduce-trunk-Commit #1344 (See [https://builds.apache.org/job/Hadoop-Mapreduce-trunk-Commit/1344/]) HADOOP-7861. changes2html.pl generates links to HADOOP, HDFS, and MAPREDUCE jiras. Contributed by Konstantin Shvachko. shv : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1205988 Files : * /hadoop/common/trunk/hadoop-common-project/hadoop-common/CHANGES.txt * /hadoop/common/trunk/hadoop-common-project/hadoop-common/src/main/docs/changes/changes2html.pl * /hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/main/docs/changes/changes2html.pl * /hadoop/common/trunk/hadoop-mapreduce-project/src/docs/changes/changes2html.pl > changes2html.pl should generate links to HADOOP, HDFS, and MAPREDUCE jiras > -- > > Key: HADOOP-7861 > URL: https://issues.apache.org/jira/browse/HADOOP-7861 > Project: Hadoop Common > Issue Type: Improvement > Components: documentation >Affects Versions: 0.20.0 >Reporter: Konstantin Shvachko >Assignee: Konstantin Shvachko > Fix For: 0.22.0 > > Attachments: changes2html.patch > > > changes2html.pl correctly generates links to HADOOP jiras only. This hasn't > been updated since projects split. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HADOOP-7861) changes2html.pl should generate links to HADOOP, HDFS, and MAPREDUCE jiras
[ https://issues.apache.org/jira/browse/HADOOP-7861?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konstantin Shvachko updated HADOOP-7861: Issue Type: Improvement (was: Bug) > changes2html.pl should generate links to HADOOP, HDFS, and MAPREDUCE jiras > -- > > Key: HADOOP-7861 > URL: https://issues.apache.org/jira/browse/HADOOP-7861 > Project: Hadoop Common > Issue Type: Improvement > Components: documentation >Affects Versions: 0.20.0 >Reporter: Konstantin Shvachko >Assignee: Konstantin Shvachko > Fix For: 0.22.0 > > Attachments: changes2html.patch > > > changes2html.pl correctly generates links to HADOOP jiras only. This hasn't > been updated since projects split. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HADOOP-7861) changes2html.pl should generate links to HADOOP, HDFS, and MAPREDUCE jiras
[ https://issues.apache.org/jira/browse/HADOOP-7861?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13156913#comment-13156913 ] Hudson commented on HADOOP-7861: Integrated in Hadoop-Hdfs-trunk-Commit #1394 (See [https://builds.apache.org/job/Hadoop-Hdfs-trunk-Commit/1394/]) HADOOP-7861. changes2html.pl generates links to HADOOP, HDFS, and MAPREDUCE jiras. Contributed by Konstantin Shvachko. shv : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1205988 Files : * /hadoop/common/trunk/hadoop-common-project/hadoop-common/CHANGES.txt * /hadoop/common/trunk/hadoop-common-project/hadoop-common/src/main/docs/changes/changes2html.pl * /hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/main/docs/changes/changes2html.pl * /hadoop/common/trunk/hadoop-mapreduce-project/src/docs/changes/changes2html.pl > changes2html.pl should generate links to HADOOP, HDFS, and MAPREDUCE jiras > -- > > Key: HADOOP-7861 > URL: https://issues.apache.org/jira/browse/HADOOP-7861 > Project: Hadoop Common > Issue Type: Bug > Components: documentation >Affects Versions: 0.20.0 >Reporter: Konstantin Shvachko >Assignee: Konstantin Shvachko > Fix For: 0.22.0 > > Attachments: changes2html.patch > > > changes2html.pl correctly generates links to HADOOP jiras only. This hasn't > been updated since projects split. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (HADOOP-7861) changes2html.pl should generate links to HADOOP, HDFS, and MAPREDUCE jiras
[ https://issues.apache.org/jira/browse/HADOOP-7861?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konstantin Shvachko resolved HADOOP-7861. - Resolution: Fixed I just committed this to trunk and branch 0.22. Please pick up for other branches if applicable. > changes2html.pl should generate links to HADOOP, HDFS, and MAPREDUCE jiras > -- > > Key: HADOOP-7861 > URL: https://issues.apache.org/jira/browse/HADOOP-7861 > Project: Hadoop Common > Issue Type: Bug > Components: documentation >Affects Versions: 0.20.0 >Reporter: Konstantin Shvachko >Assignee: Konstantin Shvachko > Fix For: 0.22.0 > > Attachments: changes2html.patch > > > changes2html.pl correctly generates links to HADOOP jiras only. This hasn't > been updated since projects split. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HADOOP-7861) changes2html.pl should generate links to HADOOP, HDFS, and MAPREDUCE jiras
[ https://issues.apache.org/jira/browse/HADOOP-7861?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13156911#comment-13156911 ] Hudson commented on HADOOP-7861: Integrated in Hadoop-Common-trunk-Commit #1321 (See [https://builds.apache.org/job/Hadoop-Common-trunk-Commit/1321/]) HADOOP-7861. changes2html.pl generates links to HADOOP, HDFS, and MAPREDUCE jiras. Contributed by Konstantin Shvachko. shv : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1205988 Files : * /hadoop/common/trunk/hadoop-common-project/hadoop-common/CHANGES.txt * /hadoop/common/trunk/hadoop-common-project/hadoop-common/src/main/docs/changes/changes2html.pl * /hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/main/docs/changes/changes2html.pl * /hadoop/common/trunk/hadoop-mapreduce-project/src/docs/changes/changes2html.pl > changes2html.pl should generate links to HADOOP, HDFS, and MAPREDUCE jiras > -- > > Key: HADOOP-7861 > URL: https://issues.apache.org/jira/browse/HADOOP-7861 > Project: Hadoop Common > Issue Type: Bug > Components: documentation >Affects Versions: 0.20.0 >Reporter: Konstantin Shvachko >Assignee: Konstantin Shvachko > Fix For: 0.22.0 > > Attachments: changes2html.patch > > > changes2html.pl correctly generates links to HADOOP jiras only. This hasn't > been updated since projects split. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HADOOP-7861) changes2html.pl should generate links to HADOOP, HDFS, and MAPREDUCE jiras
[ https://issues.apache.org/jira/browse/HADOOP-7861?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konstantin Shvachko updated HADOOP-7861: Attachment: changes2html.patch Will apply to all three projects instead of creating 3 jiras, as all 3 files are identical. > changes2html.pl should generate links to HADOOP, HDFS, and MAPREDUCE jiras > -- > > Key: HADOOP-7861 > URL: https://issues.apache.org/jira/browse/HADOOP-7861 > Project: Hadoop Common > Issue Type: Bug > Components: documentation >Affects Versions: 0.20.0 >Reporter: Konstantin Shvachko >Assignee: Konstantin Shvachko > Fix For: 0.22.0 > > Attachments: changes2html.patch > > > changes2html.pl correctly generates links to HADOOP jiras only. This hasn't > been updated since projects split. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (HADOOP-7861) changes2html.pl should generate links to HADOOP, HDFS, and MAPREDUCE jiras
changes2html.pl should generate links to HADOOP, HDFS, and MAPREDUCE jiras -- Key: HADOOP-7861 URL: https://issues.apache.org/jira/browse/HADOOP-7861 Project: Hadoop Common Issue Type: Bug Components: documentation Affects Versions: 0.20.0 Reporter: Konstantin Shvachko Assignee: Konstantin Shvachko Fix For: 0.22.0 changes2html.pl correctly generates links to HADOOP jiras only. This hasn't been updated since projects split. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HADOOP-7851) Configuration.getClasses() never returns the default value.
[ https://issues.apache.org/jira/browse/HADOOP-7851?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13156867#comment-13156867 ] Uma Maheswara Rao G commented on HADOOP-7851: - Javadoc comments are not from this patch! let me check. > Configuration.getClasses() never returns the default value. > --- > > Key: HADOOP-7851 > URL: https://issues.apache.org/jira/browse/HADOOP-7851 > Project: Hadoop Common > Issue Type: Bug > Components: conf >Affects Versions: 0.23.0 >Reporter: Amar Kamat >Assignee: Uma Maheswara Rao G > Labels: configuration > Fix For: 0.24.0, 0.23.1 > > Attachments: HADOOP-7851.patch, HADOOP-7851.patch > > > Configuration.getClasses() never returns the default value. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HADOOP-1381) The distance between sync blocks in SequenceFiles should be configurable rather than hard coded to 2000 bytes
[ https://issues.apache.org/jira/browse/HADOOP-1381?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13156857#comment-13156857 ] Todd Lipcon commented on HADOOP-1381: - hm, if you set it to 0, it will write a sync marker between every record? Don't worry about renaming the variable, seems like too much effort for little gain. > The distance between sync blocks in SequenceFiles should be configurable > rather than hard coded to 2000 bytes > - > > Key: HADOOP-1381 > URL: https://issues.apache.org/jira/browse/HADOOP-1381 > Project: Hadoop Common > Issue Type: Improvement > Components: io >Affects Versions: 0.22.0 >Reporter: Owen O'Malley >Assignee: Harsh J > Fix For: 0.24.0 > > Attachments: HADOOP-1381.r1.diff, HADOOP-1381.r2.diff, > HADOOP-1381.r3.diff, HADOOP-1381.r4.diff > > > Currently SequenceFiles put in sync blocks every 2000 bytes. It would be much > better if it was configurable with a much higher default (1mb or so?). -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HADOOP-7851) Configuration.getClasses() never returns the default value.
[ https://issues.apache.org/jira/browse/HADOOP-7851?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13156856#comment-13156856 ] Hadoop QA commented on HADOOP-7851: --- -1 overall. Here are the results of testing the latest attachment http://issues.apache.org/jira/secure/attachment/12505028/HADOOP-7851.patch against trunk revision . +1 @author. The patch does not contain any @author tags. +1 tests included. The patch appears to include 3 new or modified tests. -1 javadoc. The javadoc tool appears to have generated 15 warning messages. +1 javac. The applied patch does not increase the total number of javac compiler warnings. +1 findbugs. The patch does not introduce any new Findbugs (version 1.3.9) warnings. +1 release audit. The applied patch does not increase the total number of release audit warnings. +1 core tests. The patch passed unit tests in . +1 contrib tests. The patch passed contrib unit tests. Test results: https://builds.apache.org/job/PreCommit-HADOOP-Build/406//testReport/ Console output: https://builds.apache.org/job/PreCommit-HADOOP-Build/406//console This message is automatically generated. > Configuration.getClasses() never returns the default value. > --- > > Key: HADOOP-7851 > URL: https://issues.apache.org/jira/browse/HADOOP-7851 > Project: Hadoop Common > Issue Type: Bug > Components: conf >Affects Versions: 0.23.0 >Reporter: Amar Kamat >Assignee: Uma Maheswara Rao G > Labels: configuration > Fix For: 0.24.0, 0.23.1 > > Attachments: HADOOP-7851.patch, HADOOP-7851.patch > > > Configuration.getClasses() never returns the default value. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HADOOP-7851) Configuration.getClasses() never returns the default value.
[ https://issues.apache.org/jira/browse/HADOOP-7851?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13156853#comment-13156853 ] Uma Maheswara Rao G commented on HADOOP-7851: - For 23 branch, we can directly merge the trunk patch because there is no code mismatches. > Configuration.getClasses() never returns the default value. > --- > > Key: HADOOP-7851 > URL: https://issues.apache.org/jira/browse/HADOOP-7851 > Project: Hadoop Common > Issue Type: Bug > Components: conf >Affects Versions: 0.23.0 >Reporter: Amar Kamat >Assignee: Uma Maheswara Rao G > Labels: configuration > Fix For: 0.24.0, 0.23.1 > > Attachments: HADOOP-7851.patch, HADOOP-7851.patch > > > Configuration.getClasses() never returns the default value. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HADOOP-7851) Configuration.getClasses() never returns the default value.
[ https://issues.apache.org/jira/browse/HADOOP-7851?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Uma Maheswara Rao G updated HADOOP-7851: Attachment: HADOOP-7851.patch > Configuration.getClasses() never returns the default value. > --- > > Key: HADOOP-7851 > URL: https://issues.apache.org/jira/browse/HADOOP-7851 > Project: Hadoop Common > Issue Type: Bug > Components: conf >Affects Versions: 0.23.0 >Reporter: Amar Kamat >Assignee: Uma Maheswara Rao G > Labels: configuration > Fix For: 0.24.0, 0.23.1 > > Attachments: HADOOP-7851.patch, HADOOP-7851.patch > > > Configuration.getClasses() never returns the default value. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HADOOP-7851) Configuration.getClasses() never returns the default value.
[
https://issues.apache.org/jira/browse/HADOOP-7851?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13156851#comment-13156851
]
Uma Maheswara Rao G commented on HADOOP-7851:
-
{quote}
Can we not test instead for an empty array and return the default value? This
way we properly reuse the getTrimmedStrings function thats already present,
instead of directly calling out the StringUtils one.
{quote}
This also should work.
{quote}
This problem exists in 0.20-security as well. Would love it if you can post a
patch for that as well?
{quote}
In 20Security205, getStrings itself will return null if collection is empty.
Collection values = getStringCollection(str);
if(values.size() == 0) {
return null;
}
I dont see problem here. Am i missing some thing here?
> Configuration.getClasses() never returns the default value.
> ---
>
> Key: HADOOP-7851
> URL: https://issues.apache.org/jira/browse/HADOOP-7851
> Project: Hadoop Common
> Issue Type: Bug
> Components: conf
>Affects Versions: 0.23.0
>Reporter: Amar Kamat
>Assignee: Uma Maheswara Rao G
> Labels: configuration
> Fix For: 0.24.0, 0.23.1
>
> Attachments: HADOOP-7851.patch
>
>
> Configuration.getClasses() never returns the default value.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HADOOP-7851) Configuration.getClasses() never returns the default value.
[ https://issues.apache.org/jira/browse/HADOOP-7851?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13156816#comment-13156816 ] Harsh J commented on HADOOP-7851: - This problem exists in 0.20-security as well. Would love it if you can post a patch for that as well? > Configuration.getClasses() never returns the default value. > --- > > Key: HADOOP-7851 > URL: https://issues.apache.org/jira/browse/HADOOP-7851 > Project: Hadoop Common > Issue Type: Bug > Components: conf >Affects Versions: 0.23.0 >Reporter: Amar Kamat >Assignee: Uma Maheswara Rao G > Labels: configuration > Fix For: 0.24.0, 0.23.1 > > Attachments: HADOOP-7851.patch > > > Configuration.getClasses() never returns the default value. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HADOOP-7851) Configuration.getClasses() never returns the default value.
[ https://issues.apache.org/jira/browse/HADOOP-7851?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13156814#comment-13156814 ] Harsh J commented on HADOOP-7851: - Can we not test instead for an empty array and return the default value? This way we properly reuse the getTrimmedStrings function thats already present, instead of directly calling out the StringUtils one. > Configuration.getClasses() never returns the default value. > --- > > Key: HADOOP-7851 > URL: https://issues.apache.org/jira/browse/HADOOP-7851 > Project: Hadoop Common > Issue Type: Bug > Components: conf >Affects Versions: 0.23.0 >Reporter: Amar Kamat >Assignee: Uma Maheswara Rao G > Labels: configuration > Fix For: 0.24.0, 0.23.1 > > Attachments: HADOOP-7851.patch > > > Configuration.getClasses() never returns the default value. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HADOOP-7851) Configuration.getClasses() never returns the default value.
[ https://issues.apache.org/jira/browse/HADOOP-7851?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13156768#comment-13156768 ] Hadoop QA commented on HADOOP-7851: --- -1 overall. Here are the results of testing the latest attachment http://issues.apache.org/jira/secure/attachment/12505005/HADOOP-7851.patch against trunk revision . +1 @author. The patch does not contain any @author tags. +1 tests included. The patch appears to include 3 new or modified tests. -1 javadoc. The javadoc tool appears to have generated 15 warning messages. +1 javac. The applied patch does not increase the total number of javac compiler warnings. +1 findbugs. The patch does not introduce any new Findbugs (version 1.3.9) warnings. +1 release audit. The applied patch does not increase the total number of release audit warnings. +1 core tests. The patch passed unit tests in . +1 contrib tests. The patch passed contrib unit tests. Test results: https://builds.apache.org/job/PreCommit-HADOOP-Build/405//testReport/ Console output: https://builds.apache.org/job/PreCommit-HADOOP-Build/405//console This message is automatically generated. > Configuration.getClasses() never returns the default value. > --- > > Key: HADOOP-7851 > URL: https://issues.apache.org/jira/browse/HADOOP-7851 > Project: Hadoop Common > Issue Type: Bug > Components: conf >Affects Versions: 0.23.0 >Reporter: Amar Kamat >Assignee: Uma Maheswara Rao G > Labels: configuration > Fix For: 0.24.0, 0.23.1 > > Attachments: HADOOP-7851.patch > > > Configuration.getClasses() never returns the default value. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HADOOP-7851) Configuration.getClasses() never returns the default value.
[ https://issues.apache.org/jira/browse/HADOOP-7851?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Uma Maheswara Rao G updated HADOOP-7851: Target Version/s: 0.24.0, 0.23.1 (was: 0.23.1, 0.24.0) Status: Patch Available (was: Open) > Configuration.getClasses() never returns the default value. > --- > > Key: HADOOP-7851 > URL: https://issues.apache.org/jira/browse/HADOOP-7851 > Project: Hadoop Common > Issue Type: Bug > Components: conf >Affects Versions: 0.23.0 >Reporter: Amar Kamat >Assignee: Uma Maheswara Rao G > Labels: configuration > Fix For: 0.24.0, 0.23.1 > > Attachments: HADOOP-7851.patch > > > Configuration.getClasses() never returns the default value. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (HADOOP-7860) tar file contains duplicate config files in etc/ and conf/
tar file contains duplicate config files in etc/ and conf/ -- Key: HADOOP-7860 URL: https://issues.apache.org/jira/browse/HADOOP-7860 Project: Hadoop Common Issue Type: Bug Components: build Affects Versions: 0.20.205.0 Environment: Debian 6.0 x64_64 java version "1.6.0_26" Java(TM) SE Runtime Environment (build 1.6.0_26-b03) Java HotSpot(TM) 64-Bit Server VM (build 20.1-b02, mixed mode) Reporter: stephen mulcahy Priority: Minor When I extract the hadoop tar file download for 0.20.205.0 I notice that it contains a set of configuration files in conf/ and what seem to be a duplicate set in etc/hadoop. There is no indication in the docs of why there are two copies of these files. In practice, the contents of conf/ seem to be used, not etc/hadoop. I would suggest removing one of these or else clarifying their purpose. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HADOOP-7358) Improve log levels when exceptions caught in RPC handler
[ https://issues.apache.org/jira/browse/HADOOP-7358?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13156701#comment-13156701 ] Hudson commented on HADOOP-7358: Integrated in Hadoop-Mapreduce-trunk #907 (See [https://builds.apache.org/job/Hadoop-Mapreduce-trunk/907/]) HADOOP-7358. Improve log levels when exceptions caught in RPC handler. Contributed by Todd Lipcon. shv : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1205697 Files : * /hadoop/common/trunk/hadoop-common-project/hadoop-common/CHANGES.txt * /hadoop/common/trunk/hadoop-common-project/hadoop-common/src/main/java/org/apache/hadoop/ipc/Server.java > Improve log levels when exceptions caught in RPC handler > > > Key: HADOOP-7358 > URL: https://issues.apache.org/jira/browse/HADOOP-7358 > Project: Hadoop Common > Issue Type: Improvement > Components: ipc >Affects Versions: 0.22.0 >Reporter: Todd Lipcon >Assignee: Todd Lipcon >Priority: Minor > Fix For: 0.22.0 > > Attachments: HADOOP-7358.trunk.patch, hadoop-7358.txt > > > When a server implementation throws an exception handling an RPC, the Handler > thread catches it and logs it before responding with the exception over the > IPC channel. This is currently done at INFO level. > I'd like to propose that, if the exception is an unchecked exception, it > should be logged at WARN level instead. This can help alert operators when > they might be hitting some kind of bug. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HADOOP-7827) jsp pages missing DOCTYPE
[ https://issues.apache.org/jira/browse/HADOOP-7827?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13156697#comment-13156697 ] Hudson commented on HADOOP-7827: Integrated in Hadoop-Mapreduce-trunk #907 (See [https://builds.apache.org/job/Hadoop-Mapreduce-trunk/907/]) HADOOP-7827 HDFS-2588 MAPREDUCE-3464. jsp pages missing DOCTYPE. Contributed by Dave Vronay. mattf : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1205519 Files : * /hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/CHANGES.txt * /hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/main/webapps/datanode/browseBlock.jsp * /hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/main/webapps/datanode/browseDirectory.jsp * /hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/main/webapps/datanode/tail.jsp * /hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/main/webapps/hdfs/corrupt_files.jsp * /hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/main/webapps/hdfs/dfshealth.jsp * /hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/main/webapps/hdfs/dfsnodelist.jsp * /hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/main/webapps/hdfs/nn_browsedfscontent.jsp * /hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/main/webapps/secondary/status.jsp * /hadoop/common/trunk/hadoop-mapreduce-project/CHANGES.txt * /hadoop/common/trunk/hadoop-mapreduce-project/src/webapps/job/analysejobhistory.jsp * /hadoop/common/trunk/hadoop-mapreduce-project/src/webapps/job/job_authorization_error.jsp * /hadoop/common/trunk/hadoop-mapreduce-project/src/webapps/job/jobblacklistedtrackers.jsp * /hadoop/common/trunk/hadoop-mapreduce-project/src/webapps/job/jobconf.jsp * /hadoop/common/trunk/hadoop-mapreduce-project/src/webapps/job/jobconf_history.jsp * /hadoop/common/trunk/hadoop-mapreduce-project/src/webapps/job/jobdetails.jsp * /hadoop/common/trunk/hadoop-mapreduce-project/src/webapps/job/jobdetailshistory.jsp * /hadoop/common/trunk/hadoop-mapreduce-project/src/webapps/job/jobfailures.jsp * /hadoop/common/trunk/hadoop-mapreduce-project/src/webapps/job/jobhistory.jsp * /hadoop/common/trunk/hadoop-mapreduce-project/src/webapps/job/jobqueue_details.jsp * /hadoop/common/trunk/hadoop-mapreduce-project/src/webapps/job/jobtasks.jsp * /hadoop/common/trunk/hadoop-mapreduce-project/src/webapps/job/jobtaskshistory.jsp * /hadoop/common/trunk/hadoop-mapreduce-project/src/webapps/job/jobtracker.jsp * /hadoop/common/trunk/hadoop-mapreduce-project/src/webapps/job/machines.jsp * /hadoop/common/trunk/hadoop-mapreduce-project/src/webapps/job/queueinfo.jsp * /hadoop/common/trunk/hadoop-mapreduce-project/src/webapps/job/queuetable.jsp * /hadoop/common/trunk/hadoop-mapreduce-project/src/webapps/job/taskdetails.jsp * /hadoop/common/trunk/hadoop-mapreduce-project/src/webapps/job/taskdetailshistory.jsp * /hadoop/common/trunk/hadoop-mapreduce-project/src/webapps/job/taskstats.jsp * /hadoop/common/trunk/hadoop-mapreduce-project/src/webapps/job/taskstatshistory.jsp * /hadoop/common/trunk/hadoop-mapreduce-project/src/webapps/task/tasktracker.jsp > jsp pages missing DOCTYPE > - > > Key: HADOOP-7827 > URL: https://issues.apache.org/jira/browse/HADOOP-7827 > Project: Hadoop Common > Issue Type: Bug >Affects Versions: 0.20.203.0 >Reporter: Dave Vronay >Assignee: Dave Vronay >Priority: Trivial > Fix For: 0.20.205.1, 0.23.1 > > Attachments: HADOOP-7827-branch-0.20-security.patch, > HADOOP-7827.patch, HADOOP-7827.patch > > Original Estimate: 168h > Remaining Estimate: 168h > > The various jsp pages in the UI are all missing a DOCTYPE declaration. This > causes the pages to render incorrectly on some browsers, such as IE9. Every > UI page should have a valid tag, such as , as their first > line. There are 31 files that need to be changed, all in the > core\src\webapps tree. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HADOOP-7827) jsp pages missing DOCTYPE
[ https://issues.apache.org/jira/browse/HADOOP-7827?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13156683#comment-13156683 ] Hudson commented on HADOOP-7827: Integrated in Hadoop-Mapreduce-0.23-Build #103 (See [https://builds.apache.org/job/Hadoop-Mapreduce-0.23-Build/103/]) HADOOP-7827 HDFS-2588 MAPREDUCE-3464. jsp pages missing DOCTYPE. Contributed by Dave Vronay. mattf : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1205529 Files : * /hadoop/common/branches/branch-0.23/hadoop-hdfs-project/hadoop-hdfs/CHANGES.txt * /hadoop/common/branches/branch-0.23/hadoop-hdfs-project/hadoop-hdfs/src/main/webapps/datanode/browseBlock.jsp * /hadoop/common/branches/branch-0.23/hadoop-hdfs-project/hadoop-hdfs/src/main/webapps/datanode/browseDirectory.jsp * /hadoop/common/branches/branch-0.23/hadoop-hdfs-project/hadoop-hdfs/src/main/webapps/datanode/tail.jsp * /hadoop/common/branches/branch-0.23/hadoop-hdfs-project/hadoop-hdfs/src/main/webapps/hdfs/corrupt_files.jsp * /hadoop/common/branches/branch-0.23/hadoop-hdfs-project/hadoop-hdfs/src/main/webapps/hdfs/dfshealth.jsp * /hadoop/common/branches/branch-0.23/hadoop-hdfs-project/hadoop-hdfs/src/main/webapps/hdfs/dfsnodelist.jsp * /hadoop/common/branches/branch-0.23/hadoop-hdfs-project/hadoop-hdfs/src/main/webapps/hdfs/nn_browsedfscontent.jsp * /hadoop/common/branches/branch-0.23/hadoop-hdfs-project/hadoop-hdfs/src/main/webapps/secondary/status.jsp * /hadoop/common/branches/branch-0.23/hadoop-mapreduce-project/CHANGES.txt * /hadoop/common/branches/branch-0.23/hadoop-mapreduce-project/src/webapps/job/analysejobhistory.jsp * /hadoop/common/branches/branch-0.23/hadoop-mapreduce-project/src/webapps/job/job_authorization_error.jsp * /hadoop/common/branches/branch-0.23/hadoop-mapreduce-project/src/webapps/job/jobblacklistedtrackers.jsp * /hadoop/common/branches/branch-0.23/hadoop-mapreduce-project/src/webapps/job/jobconf.jsp * /hadoop/common/branches/branch-0.23/hadoop-mapreduce-project/src/webapps/job/jobconf_history.jsp * /hadoop/common/branches/branch-0.23/hadoop-mapreduce-project/src/webapps/job/jobdetails.jsp * /hadoop/common/branches/branch-0.23/hadoop-mapreduce-project/src/webapps/job/jobdetailshistory.jsp * /hadoop/common/branches/branch-0.23/hadoop-mapreduce-project/src/webapps/job/jobfailures.jsp * /hadoop/common/branches/branch-0.23/hadoop-mapreduce-project/src/webapps/job/jobhistory.jsp * /hadoop/common/branches/branch-0.23/hadoop-mapreduce-project/src/webapps/job/jobqueue_details.jsp * /hadoop/common/branches/branch-0.23/hadoop-mapreduce-project/src/webapps/job/jobtasks.jsp * /hadoop/common/branches/branch-0.23/hadoop-mapreduce-project/src/webapps/job/jobtaskshistory.jsp * /hadoop/common/branches/branch-0.23/hadoop-mapreduce-project/src/webapps/job/jobtracker.jsp * /hadoop/common/branches/branch-0.23/hadoop-mapreduce-project/src/webapps/job/machines.jsp * /hadoop/common/branches/branch-0.23/hadoop-mapreduce-project/src/webapps/job/queueinfo.jsp * /hadoop/common/branches/branch-0.23/hadoop-mapreduce-project/src/webapps/job/queuetable.jsp * /hadoop/common/branches/branch-0.23/hadoop-mapreduce-project/src/webapps/job/taskdetails.jsp * /hadoop/common/branches/branch-0.23/hadoop-mapreduce-project/src/webapps/job/taskdetailshistory.jsp * /hadoop/common/branches/branch-0.23/hadoop-mapreduce-project/src/webapps/job/taskstats.jsp * /hadoop/common/branches/branch-0.23/hadoop-mapreduce-project/src/webapps/job/taskstatshistory.jsp * /hadoop/common/branches/branch-0.23/hadoop-mapreduce-project/src/webapps/task/tasktracker.jsp > jsp pages missing DOCTYPE > - > > Key: HADOOP-7827 > URL: https://issues.apache.org/jira/browse/HADOOP-7827 > Project: Hadoop Common > Issue Type: Bug >Affects Versions: 0.20.203.0 >Reporter: Dave Vronay >Assignee: Dave Vronay >Priority: Trivial > Fix For: 0.20.205.1, 0.23.1 > > Attachments: HADOOP-7827-branch-0.20-security.patch, > HADOOP-7827.patch, HADOOP-7827.patch > > Original Estimate: 168h > Remaining Estimate: 168h > > The various jsp pages in the UI are all missing a DOCTYPE declaration. This > causes the pages to render incorrectly on some browsers, such as IE9. Every > UI page should have a valid tag, such as , as their first > line. There are 31 files that need to be changed, all in the > core\src\webapps tree. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HADOOP-7358) Improve log levels when exceptions caught in RPC handler
[ https://issues.apache.org/jira/browse/HADOOP-7358?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13156674#comment-13156674 ] Hudson commented on HADOOP-7358: Integrated in Hadoop-Hdfs-trunk #873 (See [https://builds.apache.org/job/Hadoop-Hdfs-trunk/873/]) HADOOP-7358. Improve log levels when exceptions caught in RPC handler. Contributed by Todd Lipcon. shv : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1205697 Files : * /hadoop/common/trunk/hadoop-common-project/hadoop-common/CHANGES.txt * /hadoop/common/trunk/hadoop-common-project/hadoop-common/src/main/java/org/apache/hadoop/ipc/Server.java > Improve log levels when exceptions caught in RPC handler > > > Key: HADOOP-7358 > URL: https://issues.apache.org/jira/browse/HADOOP-7358 > Project: Hadoop Common > Issue Type: Improvement > Components: ipc >Affects Versions: 0.22.0 >Reporter: Todd Lipcon >Assignee: Todd Lipcon >Priority: Minor > Fix For: 0.22.0 > > Attachments: HADOOP-7358.trunk.patch, hadoop-7358.txt > > > When a server implementation throws an exception handling an RPC, the Handler > thread catches it and logs it before responding with the exception over the > IPC channel. This is currently done at INFO level. > I'd like to propose that, if the exception is an unchecked exception, it > should be logged at WARN level instead. This can help alert operators when > they might be hitting some kind of bug. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HADOOP-7827) jsp pages missing DOCTYPE
[ https://issues.apache.org/jira/browse/HADOOP-7827?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13156670#comment-13156670 ] Hudson commented on HADOOP-7827: Integrated in Hadoop-Hdfs-trunk #873 (See [https://builds.apache.org/job/Hadoop-Hdfs-trunk/873/]) HADOOP-7827 HDFS-2588 MAPREDUCE-3464. jsp pages missing DOCTYPE. Contributed by Dave Vronay. mattf : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1205519 Files : * /hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/CHANGES.txt * /hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/main/webapps/datanode/browseBlock.jsp * /hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/main/webapps/datanode/browseDirectory.jsp * /hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/main/webapps/datanode/tail.jsp * /hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/main/webapps/hdfs/corrupt_files.jsp * /hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/main/webapps/hdfs/dfshealth.jsp * /hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/main/webapps/hdfs/dfsnodelist.jsp * /hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/main/webapps/hdfs/nn_browsedfscontent.jsp * /hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/main/webapps/secondary/status.jsp * /hadoop/common/trunk/hadoop-mapreduce-project/CHANGES.txt * /hadoop/common/trunk/hadoop-mapreduce-project/src/webapps/job/analysejobhistory.jsp * /hadoop/common/trunk/hadoop-mapreduce-project/src/webapps/job/job_authorization_error.jsp * /hadoop/common/trunk/hadoop-mapreduce-project/src/webapps/job/jobblacklistedtrackers.jsp * /hadoop/common/trunk/hadoop-mapreduce-project/src/webapps/job/jobconf.jsp * /hadoop/common/trunk/hadoop-mapreduce-project/src/webapps/job/jobconf_history.jsp * /hadoop/common/trunk/hadoop-mapreduce-project/src/webapps/job/jobdetails.jsp * /hadoop/common/trunk/hadoop-mapreduce-project/src/webapps/job/jobdetailshistory.jsp * /hadoop/common/trunk/hadoop-mapreduce-project/src/webapps/job/jobfailures.jsp * /hadoop/common/trunk/hadoop-mapreduce-project/src/webapps/job/jobhistory.jsp * /hadoop/common/trunk/hadoop-mapreduce-project/src/webapps/job/jobqueue_details.jsp * /hadoop/common/trunk/hadoop-mapreduce-project/src/webapps/job/jobtasks.jsp * /hadoop/common/trunk/hadoop-mapreduce-project/src/webapps/job/jobtaskshistory.jsp * /hadoop/common/trunk/hadoop-mapreduce-project/src/webapps/job/jobtracker.jsp * /hadoop/common/trunk/hadoop-mapreduce-project/src/webapps/job/machines.jsp * /hadoop/common/trunk/hadoop-mapreduce-project/src/webapps/job/queueinfo.jsp * /hadoop/common/trunk/hadoop-mapreduce-project/src/webapps/job/queuetable.jsp * /hadoop/common/trunk/hadoop-mapreduce-project/src/webapps/job/taskdetails.jsp * /hadoop/common/trunk/hadoop-mapreduce-project/src/webapps/job/taskdetailshistory.jsp * /hadoop/common/trunk/hadoop-mapreduce-project/src/webapps/job/taskstats.jsp * /hadoop/common/trunk/hadoop-mapreduce-project/src/webapps/job/taskstatshistory.jsp * /hadoop/common/trunk/hadoop-mapreduce-project/src/webapps/task/tasktracker.jsp > jsp pages missing DOCTYPE > - > > Key: HADOOP-7827 > URL: https://issues.apache.org/jira/browse/HADOOP-7827 > Project: Hadoop Common > Issue Type: Bug >Affects Versions: 0.20.203.0 >Reporter: Dave Vronay >Assignee: Dave Vronay >Priority: Trivial > Fix For: 0.20.205.1, 0.23.1 > > Attachments: HADOOP-7827-branch-0.20-security.patch, > HADOOP-7827.patch, HADOOP-7827.patch > > Original Estimate: 168h > Remaining Estimate: 168h > > The various jsp pages in the UI are all missing a DOCTYPE declaration. This > causes the pages to render incorrectly on some browsers, such as IE9. Every > UI page should have a valid tag, such as , as their first > line. There are 31 files that need to be changed, all in the > core\src\webapps tree. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HADOOP-7827) jsp pages missing DOCTYPE
[ https://issues.apache.org/jira/browse/HADOOP-7827?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13156661#comment-13156661 ] Hudson commented on HADOOP-7827: Integrated in Hadoop-Hdfs-0.23-Build #86 (See [https://builds.apache.org/job/Hadoop-Hdfs-0.23-Build/86/]) HADOOP-7827 HDFS-2588 MAPREDUCE-3464. jsp pages missing DOCTYPE. Contributed by Dave Vronay. mattf : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1205529 Files : * /hadoop/common/branches/branch-0.23/hadoop-hdfs-project/hadoop-hdfs/CHANGES.txt * /hadoop/common/branches/branch-0.23/hadoop-hdfs-project/hadoop-hdfs/src/main/webapps/datanode/browseBlock.jsp * /hadoop/common/branches/branch-0.23/hadoop-hdfs-project/hadoop-hdfs/src/main/webapps/datanode/browseDirectory.jsp * /hadoop/common/branches/branch-0.23/hadoop-hdfs-project/hadoop-hdfs/src/main/webapps/datanode/tail.jsp * /hadoop/common/branches/branch-0.23/hadoop-hdfs-project/hadoop-hdfs/src/main/webapps/hdfs/corrupt_files.jsp * /hadoop/common/branches/branch-0.23/hadoop-hdfs-project/hadoop-hdfs/src/main/webapps/hdfs/dfshealth.jsp * /hadoop/common/branches/branch-0.23/hadoop-hdfs-project/hadoop-hdfs/src/main/webapps/hdfs/dfsnodelist.jsp * /hadoop/common/branches/branch-0.23/hadoop-hdfs-project/hadoop-hdfs/src/main/webapps/hdfs/nn_browsedfscontent.jsp * /hadoop/common/branches/branch-0.23/hadoop-hdfs-project/hadoop-hdfs/src/main/webapps/secondary/status.jsp * /hadoop/common/branches/branch-0.23/hadoop-mapreduce-project/CHANGES.txt * /hadoop/common/branches/branch-0.23/hadoop-mapreduce-project/src/webapps/job/analysejobhistory.jsp * /hadoop/common/branches/branch-0.23/hadoop-mapreduce-project/src/webapps/job/job_authorization_error.jsp * /hadoop/common/branches/branch-0.23/hadoop-mapreduce-project/src/webapps/job/jobblacklistedtrackers.jsp * /hadoop/common/branches/branch-0.23/hadoop-mapreduce-project/src/webapps/job/jobconf.jsp * /hadoop/common/branches/branch-0.23/hadoop-mapreduce-project/src/webapps/job/jobconf_history.jsp * /hadoop/common/branches/branch-0.23/hadoop-mapreduce-project/src/webapps/job/jobdetails.jsp * /hadoop/common/branches/branch-0.23/hadoop-mapreduce-project/src/webapps/job/jobdetailshistory.jsp * /hadoop/common/branches/branch-0.23/hadoop-mapreduce-project/src/webapps/job/jobfailures.jsp * /hadoop/common/branches/branch-0.23/hadoop-mapreduce-project/src/webapps/job/jobhistory.jsp * /hadoop/common/branches/branch-0.23/hadoop-mapreduce-project/src/webapps/job/jobqueue_details.jsp * /hadoop/common/branches/branch-0.23/hadoop-mapreduce-project/src/webapps/job/jobtasks.jsp * /hadoop/common/branches/branch-0.23/hadoop-mapreduce-project/src/webapps/job/jobtaskshistory.jsp * /hadoop/common/branches/branch-0.23/hadoop-mapreduce-project/src/webapps/job/jobtracker.jsp * /hadoop/common/branches/branch-0.23/hadoop-mapreduce-project/src/webapps/job/machines.jsp * /hadoop/common/branches/branch-0.23/hadoop-mapreduce-project/src/webapps/job/queueinfo.jsp * /hadoop/common/branches/branch-0.23/hadoop-mapreduce-project/src/webapps/job/queuetable.jsp * /hadoop/common/branches/branch-0.23/hadoop-mapreduce-project/src/webapps/job/taskdetails.jsp * /hadoop/common/branches/branch-0.23/hadoop-mapreduce-project/src/webapps/job/taskdetailshistory.jsp * /hadoop/common/branches/branch-0.23/hadoop-mapreduce-project/src/webapps/job/taskstats.jsp * /hadoop/common/branches/branch-0.23/hadoop-mapreduce-project/src/webapps/job/taskstatshistory.jsp * /hadoop/common/branches/branch-0.23/hadoop-mapreduce-project/src/webapps/task/tasktracker.jsp > jsp pages missing DOCTYPE > - > > Key: HADOOP-7827 > URL: https://issues.apache.org/jira/browse/HADOOP-7827 > Project: Hadoop Common > Issue Type: Bug >Affects Versions: 0.20.203.0 >Reporter: Dave Vronay >Assignee: Dave Vronay >Priority: Trivial > Fix For: 0.20.205.1, 0.23.1 > > Attachments: HADOOP-7827-branch-0.20-security.patch, > HADOOP-7827.patch, HADOOP-7827.patch > > Original Estimate: 168h > Remaining Estimate: 168h > > The various jsp pages in the UI are all missing a DOCTYPE declaration. This > causes the pages to render incorrectly on some browsers, such as IE9. Every > UI page should have a valid tag, such as , as their first > line. There are 31 files that need to be changed, all in the > core\src\webapps tree. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HADOOP-1381) The distance between sync blocks in SequenceFiles should be configurable rather than hard coded to 2000 bytes
[ https://issues.apache.org/jira/browse/HADOOP-1381?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13156660#comment-13156660 ] Harsh J commented on HADOOP-1381: - Todd, - The sync _interval_ can be arbitrary I think, can even be 0. Should not be negative, so I'll add a check for that instead. Or do you think its better if we limit the interval to a minimum? Writer tests pass with 0 no problem. - SYNC_INTERVAL is being used by MAPREDUCE right now, and I'll have to carry this out as a cross-project JIRA+patch. > The distance between sync blocks in SequenceFiles should be configurable > rather than hard coded to 2000 bytes > - > > Key: HADOOP-1381 > URL: https://issues.apache.org/jira/browse/HADOOP-1381 > Project: Hadoop Common > Issue Type: Improvement > Components: io >Affects Versions: 0.22.0 >Reporter: Owen O'Malley >Assignee: Harsh J > Fix For: 0.24.0 > > Attachments: HADOOP-1381.r1.diff, HADOOP-1381.r2.diff, > HADOOP-1381.r3.diff, HADOOP-1381.r4.diff > > > Currently SequenceFiles put in sync blocks every 2000 bytes. It would be much > better if it was configurable with a much higher default (1mb or so?). -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HADOOP-7851) Configuration.getClasses() never returns the default value.
[ https://issues.apache.org/jira/browse/HADOOP-7851?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Uma Maheswara Rao G updated HADOOP-7851: Attachment: HADOOP-7851.patch Updated the patch for trunk! > Configuration.getClasses() never returns the default value. > --- > > Key: HADOOP-7851 > URL: https://issues.apache.org/jira/browse/HADOOP-7851 > Project: Hadoop Common > Issue Type: Bug > Components: conf >Affects Versions: 0.23.0 >Reporter: Amar Kamat >Assignee: Uma Maheswara Rao G > Labels: configuration > Fix For: 0.24.0, 0.23.1 > > Attachments: HADOOP-7851.patch > > > Configuration.getClasses() never returns the default value. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HADOOP-7358) Improve log levels when exceptions caught in RPC handler
[ https://issues.apache.org/jira/browse/HADOOP-7358?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13156607#comment-13156607 ] Hudson commented on HADOOP-7358: Integrated in Hadoop-Common-22-branch #99 (See [https://builds.apache.org/job/Hadoop-Common-22-branch/99/]) HADOOP-7358. Improve log levels when exceptions caught in RPC handler. Contributed by Todd Lipcon. shv : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1205699 Files : * /hadoop/common/branches/branch-0.22/common/CHANGES.txt * /hadoop/common/branches/branch-0.22/common/src/java/org/apache/hadoop/ipc/Server.java > Improve log levels when exceptions caught in RPC handler > > > Key: HADOOP-7358 > URL: https://issues.apache.org/jira/browse/HADOOP-7358 > Project: Hadoop Common > Issue Type: Improvement > Components: ipc >Affects Versions: 0.22.0 >Reporter: Todd Lipcon >Assignee: Todd Lipcon >Priority: Minor > Fix For: 0.22.0 > > Attachments: HADOOP-7358.trunk.patch, hadoop-7358.txt > > > When a server implementation throws an exception handling an RPC, the Handler > thread catches it and logs it before responding with the exception over the > IPC channel. This is currently done at INFO level. > I'd like to propose that, if the exception is an unchecked exception, it > should be logged at WARN level instead. This can help alert operators when > they might be hitting some kind of bug. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HADOOP-7845) Link to downloads page from hadoop.apache.org
[ https://issues.apache.org/jira/browse/HADOOP-7845?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13156592#comment-13156592 ] Hadoop QA commented on HADOOP-7845: --- -1 overall. Here are the results of testing the latest attachment http://issues.apache.org/jira/secure/attachment/12504942/HADOOP-7845.patch against trunk revision . +1 @author. The patch does not contain any @author tags. +0 tests included. The patch appears to be a documentation patch that doesn't require tests. -1 patch. The patch command could not apply the patch. Console output: https://builds.apache.org/job/PreCommit-HADOOP-Build/404//console This message is automatically generated. > Link to downloads page from hadoop.apache.org > - > > Key: HADOOP-7845 > URL: https://issues.apache.org/jira/browse/HADOOP-7845 > Project: Hadoop Common > Issue Type: Improvement > Components: documentation >Reporter: Joe Crobak >Assignee: Joe Crobak >Priority: Minor > Attachments: HADOOP-7845.patch > > > It would be nice to have a new section on the main page that links to > http://hadoop.apache.org/common/releases.html. Even better would be to have a > tab on the top labeled "Download" -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HADOOP-7846) download pages for mapred/hdfs don't match hadoop-common
[ https://issues.apache.org/jira/browse/HADOOP-7846?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13156587#comment-13156587 ] Arun C Murthy commented on HADOOP-7846: --- For now, a simple fix would be to point to common/releases.html from both hdfs and mapreduce. Thoughts? Joe - do you want to provide a patch for that? Thanks. > download pages for mapred/hdfs don't match hadoop-common > > > Key: HADOOP-7846 > URL: https://issues.apache.org/jira/browse/HADOOP-7846 > Project: Hadoop Common > Issue Type: Bug > Components: documentation >Reporter: Joe Crobak >Priority: Minor > > http://hadoop.apache.org/hdfs/releases.html > http://hadoop.apache.org/mapreduce/releases.html > don't match > http://hadoop.apache.org/common/releases.html > the common/releases.html page has a nice description of the current status > (stable, alpha, beta) of each release, and without it users get confused. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HADOOP-7845) Link to downloads page from hadoop.apache.org
[ https://issues.apache.org/jira/browse/HADOOP-7845?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arun C Murthy updated HADOOP-7845: -- Status: Patch Available (was: Open) > Link to downloads page from hadoop.apache.org > - > > Key: HADOOP-7845 > URL: https://issues.apache.org/jira/browse/HADOOP-7845 > Project: Hadoop Common > Issue Type: Improvement > Components: documentation >Reporter: Joe Crobak >Assignee: Joe Crobak >Priority: Minor > Attachments: HADOOP-7845.patch > > > It would be nice to have a new section on the main page that links to > http://hadoop.apache.org/common/releases.html. Even better would be to have a > tab on the top labeled "Download" -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Assigned] (HADOOP-7845) Link to downloads page from hadoop.apache.org
[ https://issues.apache.org/jira/browse/HADOOP-7845?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arun C Murthy reassigned HADOOP-7845: - Assignee: Joe Crobak > Link to downloads page from hadoop.apache.org > - > > Key: HADOOP-7845 > URL: https://issues.apache.org/jira/browse/HADOOP-7845 > Project: Hadoop Common > Issue Type: Improvement > Components: documentation >Reporter: Joe Crobak >Assignee: Joe Crobak >Priority: Minor > Attachments: HADOOP-7845.patch > > > It would be nice to have a new section on the main page that links to > http://hadoop.apache.org/common/releases.html. Even better would be to have a > tab on the top labeled "Download" -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
