[jira] [Updated] (HADOOP-9463) branch-1-win fails to build with OpenJDK7
[ https://issues.apache.org/jira/browse/HADOOP-9463?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ivan Mitic updated HADOOP-9463: --- Status: Patch Available (was: Open) branch-1-win fails to build with OpenJDK7 - Key: HADOOP-9463 URL: https://issues.apache.org/jira/browse/HADOOP-9463 Project: Hadoop Common Issue Type: Bug Reporter: Ivan Mitic Assignee: Ivan Mitic Fix For: 1-win Attachments: HADOOP-9463.branch-1-win.jdk7.patch Build fails with the following error: I:\svn\trunk_rebase\hadoop-common [branch-1-win] ant clean winpkg Buildfile: I:\svn\trunk_rebase\hadoop-common\build.xml BUILD FAILED I:\svn\trunk_rebase\hadoop-common\build.xml:87: Unable to create javax script engine for javascript -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HADOOP-9463) branch-1-win fails to build with OpenJDK7
[
https://issues.apache.org/jira/browse/HADOOP-9463?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13626316#comment-13626316
]
Hadoop QA commented on HADOOP-9463:
---
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12577408/HADOOP-9463.branch-1-win.jdk7.patch
against trunk revision .
{color:red}-1 patch{color}. The patch command could not apply the patch.
Console output:
https://builds.apache.org/job/PreCommit-HADOOP-Build/2429//console
This message is automatically generated.
branch-1-win fails to build with OpenJDK7
-
Key: HADOOP-9463
URL: https://issues.apache.org/jira/browse/HADOOP-9463
Project: Hadoop Common
Issue Type: Bug
Reporter: Ivan Mitic
Assignee: Ivan Mitic
Fix For: 1-win
Attachments: HADOOP-9463.branch-1-win.jdk7.patch
Build fails with the following error:
I:\svn\trunk_rebase\hadoop-common [branch-1-win] ant clean winpkg
Buildfile: I:\svn\trunk_rebase\hadoop-common\build.xml
BUILD FAILED
I:\svn\trunk_rebase\hadoop-common\build.xml:87: Unable to create javax script
engine for javascript
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HADOOP-9233) Cover package org.apache.hadoop.compress.zlib with unit tests
[ https://issues.apache.org/jira/browse/HADOOP-9233?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vadim Bondarev updated HADOOP-9233: --- Attachment: HADOOP-9233-trunk-d.patch Cover package org.apache.hadoop.compress.zlib with unit tests - Key: HADOOP-9233 URL: https://issues.apache.org/jira/browse/HADOOP-9233 Project: Hadoop Common Issue Type: Test Affects Versions: 3.0.0, 2.0.3-alpha, 0.23.6 Reporter: Vadim Bondarev Assignee: Vadim Bondarev Attachments: HADOOP-9233-branch-0.23-b.patch, HADOOP-9233-branch-2-a.patch, HADOOP-9233-branch-2-b.patch, HADOOP-9233-trunk-a.patch, HADOOP-9233-trunk-b.patch, HADOOP-9233-trunk-c.patch, HADOOP-9233-trunk-d.patch -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HADOOP-9233) Cover package org.apache.hadoop.compress.zlib with unit tests
[ https://issues.apache.org/jira/browse/HADOOP-9233?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13626513#comment-13626513 ] Vadim Bondarev commented on HADOOP-9233: 1.ZlibCompressor/ZlibDecompressor was replaced in TestZlibCompressorDecompressor class 2.Used ZlibFactory for check on native code 3.Created static function generate instead ByteGenerator class Cover package org.apache.hadoop.compress.zlib with unit tests - Key: HADOOP-9233 URL: https://issues.apache.org/jira/browse/HADOOP-9233 Project: Hadoop Common Issue Type: Test Affects Versions: 3.0.0, 2.0.3-alpha, 0.23.6 Reporter: Vadim Bondarev Assignee: Vadim Bondarev Attachments: HADOOP-9233-branch-0.23-b.patch, HADOOP-9233-branch-2-a.patch, HADOOP-9233-branch-2-b.patch, HADOOP-9233-trunk-a.patch, HADOOP-9233-trunk-b.patch, HADOOP-9233-trunk-c.patch, HADOOP-9233-trunk-d.patch -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HADOOP-9078) enhance unit-test coverage of class org.apache.hadoop.fs.FileContext
[ https://issues.apache.org/jira/browse/HADOOP-9078?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ivan A. Veselovsky updated HADOOP-9078: --- Attachment: HADOOP-9078-trunk--N6.patch new patch for trunk: 1) fixed merge conflict; 2) reverted changes complementary to fix H-9357 since that fix was rolled back from trunk; enhance unit-test coverage of class org.apache.hadoop.fs.FileContext Key: HADOOP-9078 URL: https://issues.apache.org/jira/browse/HADOOP-9078 Project: Hadoop Common Issue Type: Test Affects Versions: 3.0.0, 2.0.3-alpha, 0.23.6 Reporter: Ivan A. Veselovsky Assignee: Ivan A. Veselovsky Attachments: HADOOP-9078--b.patch, HADOOP-9078-branch-0.23.patch, HADOOP-9078-branch-2--b.patch, HADOOP-9078-branch-2--c.patch, HADOOP-9078-branch-2--N1.patch, HADOOP-9078-branch-2--N2.patch, HADOOP-9078-branch-2.patch, HADOOP-9078.patch, HADOOP-9078-patch-from-[trunk-gd]-to-[fb-HADOOP-9078-trunk-gd]-N1.patch, HADOOP-9078-trunk--N1.patch, HADOOP-9078-trunk--N2.patch, HADOOP-9078-trunk--N6.patch -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HADOOP-9222) Cover package with org.apache.hadoop.io.lz4 unit tests
[ https://issues.apache.org/jira/browse/HADOOP-9222?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vadim Bondarev updated HADOOP-9222: --- Attachment: HADOOP-9222-trunk-c.patch Cover package with org.apache.hadoop.io.lz4 unit tests -- Key: HADOOP-9222 URL: https://issues.apache.org/jira/browse/HADOOP-9222 Project: Hadoop Common Issue Type: Test Affects Versions: 3.0.0, 2.0.3-alpha, 0.23.6 Reporter: Vadim Bondarev Assignee: Vadim Bondarev Attachments: HADOOP-9222-branch-0.23-a.patch, HADOOP-9222-branch-0.23-b.patch, HADOOP-9222-branch-2-a.patch, HADOOP-9222-branch-2-b.patch, HADOOP-9222-trunk-a.patch, HADOOP-9222-trunk-b.patch, HADOOP-9222-trunk-c.patch Add test class TestLz4CompressorDecompressor with method for Lz4Compressor, Lz4Decompressor testing -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HADOOP-9222) Cover package with org.apache.hadoop.io.lz4 unit tests
[ https://issues.apache.org/jira/browse/HADOOP-9222?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13626540#comment-13626540 ] Vadim Bondarev commented on HADOOP-9222: New patch version is available 1. BytesGenerator class was been replaced with a static generate function 2. Lz4Codec.isNativeCodeLoaded instead NativeCodeLoader methods Cover package with org.apache.hadoop.io.lz4 unit tests -- Key: HADOOP-9222 URL: https://issues.apache.org/jira/browse/HADOOP-9222 Project: Hadoop Common Issue Type: Test Affects Versions: 3.0.0, 2.0.3-alpha, 0.23.6 Reporter: Vadim Bondarev Assignee: Vadim Bondarev Attachments: HADOOP-9222-branch-0.23-a.patch, HADOOP-9222-branch-0.23-b.patch, HADOOP-9222-branch-2-a.patch, HADOOP-9222-branch-2-b.patch, HADOOP-9222-trunk-a.patch, HADOOP-9222-trunk-b.patch, HADOOP-9222-trunk-c.patch Add test class TestLz4CompressorDecompressor with method for Lz4Compressor, Lz4Decompressor testing -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HADOOP-9199) Cover package org.apache.hadoop.io with unit tests
[ https://issues.apache.org/jira/browse/HADOOP-9199?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Graves updated HADOOP-9199: -- Assignee: Vadim Bondarev Cover package org.apache.hadoop.io with unit tests -- Key: HADOOP-9199 URL: https://issues.apache.org/jira/browse/HADOOP-9199 Project: Hadoop Common Issue Type: Test Affects Versions: 3.0.0, 2.0.3-alpha, 0.23.6 Reporter: Vadim Bondarev Assignee: Vadim Bondarev Attachments: HADOOP-9199-branch-0.23-a.patch, HADOOP-9199-branch-0.23-b.patch, HADOOP-9199-branch-0.23-c.patch, HADOOP-9199-branch-0.23-e.patch, HADOOP-9199-branch-2-a.patch, HADOOP-9199-branch-2-b.patch, HADOOP-9199-branch-2-c.patch, HADOOP-9199-branch-2-e.patch, HADOOP-9199-trunk-a.patch, HADOOP-9199-trunk-b.patch, HADOOP-9199-trunk-c.patch, HADOOP-9199-trunk-e.patch -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HADOOP-9225) Cover package org.apache.hadoop.compress.Snappy
[ https://issues.apache.org/jira/browse/HADOOP-9225?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Graves updated HADOOP-9225: -- Assignee: Vadim Bondarev Cover package org.apache.hadoop.compress.Snappy --- Key: HADOOP-9225 URL: https://issues.apache.org/jira/browse/HADOOP-9225 Project: Hadoop Common Issue Type: Test Affects Versions: 3.0.0, 2.0.3-alpha, 0.23.6 Reporter: Vadim Bondarev Assignee: Vadim Bondarev Attachments: HADOOP-9225-branch-0.23-a.patch, HADOOP-9225-branch-2-a.patch, HADOOP-9225-branch-2-b.patch, HADOOP-9225-branch-2-c.patch, HADOOP-9225-trunk-a.patch, HADOOP-9225-trunk-b.patch, HADOOP-9225-trunk-c.patch -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HADOOP-9219) coverage fixing for org.apache.hadoop.tools.rumen
[ https://issues.apache.org/jira/browse/HADOOP-9219?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Graves updated HADOOP-9219: -- Assignee: Aleksey Gorshkov coverage fixing for org.apache.hadoop.tools.rumen - Key: HADOOP-9219 URL: https://issues.apache.org/jira/browse/HADOOP-9219 Project: Hadoop Common Issue Type: Test Components: tools Affects Versions: 3.0.0, 2.0.3-alpha, 0.23.6 Reporter: Aleksey Gorshkov Assignee: Aleksey Gorshkov Attachments: HADOOP-9219-trunk-a.patch, HADOOP-9219-trunk-b.patch, HADOOP-9219-trunk.patch Original Estimate: 168h Remaining Estimate: 168h coverage fixing for org.apache.hadoop.tools.rumen HADOOP-9219-trunk.patch for trunk, brunch-2 and branch-0.23 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HADOOP-9254) Cover packages org.apache.hadoop.util.bloom, org.apache.hadoop.util.hash
[ https://issues.apache.org/jira/browse/HADOOP-9254?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Graves updated HADOOP-9254: -- Assignee: Vadim Bondarev Cover packages org.apache.hadoop.util.bloom, org.apache.hadoop.util.hash Key: HADOOP-9254 URL: https://issues.apache.org/jira/browse/HADOOP-9254 Project: Hadoop Common Issue Type: Test Affects Versions: 3.0.0, 2.0.3-alpha, 0.23.6 Reporter: Vadim Bondarev Assignee: Vadim Bondarev Attachments: HADOOP-9254-branch-0.23-a.patch, HADOOP-9254-branch-0.23-c.patch, HADOOP-9254-branch-2-a.patch, HADOOP-9254-branch-2-b.patch, HADOOP-9254-trunk-a.patch, HADOOP-9254-trunk-b.patch -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HADOOP-9345) fix coverage org.apache.hadoop.fs.ftp
[ https://issues.apache.org/jira/browse/HADOOP-9345?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Graves updated HADOOP-9345: -- Assignee: Aleksey Gorshkov fix coverage org.apache.hadoop.fs.ftp -- Key: HADOOP-9345 URL: https://issues.apache.org/jira/browse/HADOOP-9345 Project: Hadoop Common Issue Type: Test Affects Versions: 3.0.0, 0.23.7, 2.0.5-beta Environment: fix coverage org.apache.hadoop.fs.ftp Reporter: Aleksey Gorshkov Assignee: Aleksey Gorshkov Attachments: YARN-434-trunk.patch fix coverage org.apache.hadoop.fs.ftp patch YARN-434-trunk.patch for trunk, branch-2, branch-0.23 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HADOOP-9360) Coverage fix for org.apache.hadoop.fs.s3
[ https://issues.apache.org/jira/browse/HADOOP-9360?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Graves updated HADOOP-9360: -- Assignee: Aleksey Gorshkov Coverage fix for org.apache.hadoop.fs.s3 Key: HADOOP-9360 URL: https://issues.apache.org/jira/browse/HADOOP-9360 Project: Hadoop Common Issue Type: Test Components: fs/s3 Affects Versions: 3.0.0, 0.23.7, 2.0.5-beta Reporter: Aleksey Gorshkov Assignee: Aleksey Gorshkov Attachments: HADOOP-9360-branch-0.23-a.patch, HADOOP-9360-branch-0.23.patch, HADOOP-9360-trunk-a.patch, HADOOP-9360-trunk.patch Coverage fix for org.apache.hadoop.fs.s3 patch HADOOP-9360-trunk.patch for trunk and branch-2 HADOOP-9360-branch-0.23.patch for branch-0.23 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HADOOP-9078) enhance unit-test coverage of class org.apache.hadoop.fs.FileContext
[
https://issues.apache.org/jira/browse/HADOOP-9078?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13626632#comment-13626632
]
Hadoop QA commented on HADOOP-9078:
---
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12577786/HADOOP-9078-trunk--N6.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 6 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}. The javadoc tool did not generate any
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 1.3.9) 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-common hadoop-hdfs-project/hadoop-hdfs.
{color:green}+1 contrib tests{color}. The patch passed contrib unit tests.
Test results:
https://builds.apache.org/job/PreCommit-HADOOP-Build/2430//testReport/
Console output:
https://builds.apache.org/job/PreCommit-HADOOP-Build/2430//console
This message is automatically generated.
enhance unit-test coverage of class org.apache.hadoop.fs.FileContext
Key: HADOOP-9078
URL: https://issues.apache.org/jira/browse/HADOOP-9078
Project: Hadoop Common
Issue Type: Test
Affects Versions: 3.0.0, 2.0.3-alpha, 0.23.6
Reporter: Ivan A. Veselovsky
Assignee: Ivan A. Veselovsky
Attachments: HADOOP-9078--b.patch, HADOOP-9078-branch-0.23.patch,
HADOOP-9078-branch-2--b.patch, HADOOP-9078-branch-2--c.patch,
HADOOP-9078-branch-2--N1.patch, HADOOP-9078-branch-2--N2.patch,
HADOOP-9078-branch-2.patch, HADOOP-9078.patch,
HADOOP-9078-patch-from-[trunk-gd]-to-[fb-HADOOP-9078-trunk-gd]-N1.patch,
HADOOP-9078-trunk--N1.patch, HADOOP-9078-trunk--N2.patch,
HADOOP-9078-trunk--N6.patch
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HADOOP-9453) Configuration.loadResource should skip empty resources
[
https://issues.apache.org/jira/browse/HADOOP-9453?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Steve Loughran updated HADOOP-9453:
---
Attachment: HADOOP-9453.patch
Incorporates HADOOP-9447 to skip files of size 0. This is not done for other
resources (classpath, URLs)
Configuration.loadResource should skip empty resources
--
Key: HADOOP-9453
URL: https://issues.apache.org/jira/browse/HADOOP-9453
Project: Hadoop Common
Issue Type: Improvement
Components: conf
Affects Versions: 3.0.0
Reporter: Steve Loughran
Priority: Minor
Attachments: HADOOP-9453.patch
YARN-535 shows that having a 0-byte {yarn-site}} file (created due to the
test itself) breaks configuration loads, as it is a default resource that no
longer parses.
The resource loader code skips missing files -it should do the same for
0-byte files.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HADOOP-9453) Configuration.loadResource should skip empty resources
[
https://issues.apache.org/jira/browse/HADOOP-9453?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Steve Loughran updated HADOOP-9453:
---
Status: Patch Available (was: Open)
Configuration.loadResource should skip empty resources
--
Key: HADOOP-9453
URL: https://issues.apache.org/jira/browse/HADOOP-9453
Project: Hadoop Common
Issue Type: Improvement
Components: conf
Affects Versions: 3.0.0
Reporter: Steve Loughran
Priority: Minor
Attachments: HADOOP-9453.patch
YARN-535 shows that having a 0-byte {yarn-site}} file (created due to the
test itself) breaks configuration loads, as it is a default resource that no
longer parses.
The resource loader code skips missing files -it should do the same for
0-byte files.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HADOOP-9346) Upgrading to protoc 2.5.0 fails the build
[
https://issues.apache.org/jira/browse/HADOOP-9346?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13626668#comment-13626668
]
Ozzie Zhang commented on HADOOP-9346:
-
whether anyone solved this issue? when I build hadoop in the three different
environments(mac, centos, debian), all results fail in this issue.
my steps:
1) git clone https://github.com/apache/hadoop-common.git
2) download http://protobuf.googlecode.com/files/protobuf-2.5.0.tar.bz2 and
install
3) run mvn package -Pdist,native,docs -DskipTests -Dtar
Upgrading to protoc 2.5.0 fails the build
-
Key: HADOOP-9346
URL: https://issues.apache.org/jira/browse/HADOOP-9346
Project: Hadoop Common
Issue Type: Task
Reporter: Harsh J
Priority: Minor
Reported over the impala lists, one of the errors received is:
{code}
src/hadoop-common-project/hadoop-common/target/generated-sources/java/org/apache/hadoop/ha/proto/ZKFCProtocolProtos.java:[104,37]
can not find symbol.
symbol： class Parser
location： package com.google.protobuf
{code}
Worth looking into as we'll eventually someday bump our protobuf deps.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HADOOP-9453) Configuration.loadResource should skip empty resources
[
https://issues.apache.org/jira/browse/HADOOP-9453?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13626680#comment-13626680
]
Hadoop QA commented on HADOOP-9453:
---
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12577803/HADOOP-9453.patch
against trunk revision .
{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}. The javadoc tool did not generate any
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 1.3.9) 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-common.
{color:green}+1 contrib tests{color}. The patch passed contrib unit tests.
Test results:
https://builds.apache.org/job/PreCommit-HADOOP-Build/2431//testReport/
Console output:
https://builds.apache.org/job/PreCommit-HADOOP-Build/2431//console
This message is automatically generated.
Configuration.loadResource should skip empty resources
--
Key: HADOOP-9453
URL: https://issues.apache.org/jira/browse/HADOOP-9453
Project: Hadoop Common
Issue Type: Improvement
Components: conf
Affects Versions: 3.0.0
Reporter: Steve Loughran
Priority: Minor
Attachments: HADOOP-9453.patch
YARN-535 shows that having a 0-byte {yarn-site}} file (created due to the
test itself) breaks configuration loads, as it is a default resource that no
longer parses.
The resource loader code skips missing files -it should do the same for
0-byte files.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HADOOP-9455) HADOOP_CLIENT_OPTS is appended twice, causing JVM failures
[
https://issues.apache.org/jira/browse/HADOOP-9455?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13626723#comment-13626723
]
Chris Nauroth commented on HADOOP-9455:
---
Hi, Sangjin. I've been reviewing this and HIVE-3936. I haven't been able to
repro this problem running just the hadoop script, but I do see how an
interaction between the hive script and the hadoop script could cause this
problem if running hive with both the --debug option and a HADOOP_CLIENT_OPTS
environment variable containing the JDWP options:
# hive with --debug option calls get_debug_params in ext/debug.sh.
# get_debug_params exports HIVE_MAIN_CLIENT_DEBUG_OPTS with value set to JDWP
options.
# hive appends HIVE_MAIN_CLIENT_DEBUG_OPTS to HADOOP_CLIENT_OPTS. If your
HADOOP_CLIENT_OPTS already contained the JDWP options, then they would be
duplicated after this step executes.
# hive service scripts like ext/hiveserver.sh and ext/jar.sh run hadoop.
# hadoop launches JVM, and we get the failure you described.
This problem would be triggered only by running hive with both --debug and
HADOOP_CLIENT_OPTS containing the JDWP options. Can you check to see if this
is how you were running it?
HADOOP_CLIENT_OPTS is appended twice, causing JVM failures
--
Key: HADOOP-9455
URL: https://issues.apache.org/jira/browse/HADOOP-9455
Project: Hadoop Common
Issue Type: Bug
Components: bin
Affects Versions: 2.0.3-alpha
Reporter: Sangjin Lee
Priority: Minor
If you set HADOOP_CLIENT_OPTS and run hadoop, you'll find that the
HADOOP_CLIENT_OPTS value gets appended twice, and leads to JVM start failures
for cases like adding debug flags.
For example,
{noformat}
HADOOP_CLIENT_OPTS='-agentlib:jdwp=transport=dt_socket,address=localhost:9009,server=y,suspend=y'
hadoop jar anything
ERROR: Cannot load this JVM TI agent twice, check your java command line for
duplicate jdwp options.
Error occurred during initialization of VM
agent library failed to init: jdwp
{noformat}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HADOOP-9455) HADOOP_CLIENT_OPTS is appended twice, causing JVM failures
[
https://issues.apache.org/jira/browse/HADOOP-9455?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13626752#comment-13626752
]
Sangjin Lee commented on HADOOP-9455:
-
[~cnauroth], I am able to reproduce it without hive (in fact I don't have hive
installed on the machine where I saw this). I can download the 2.0.3-alpha
build into a new directory, and reproduce this.
{noformat}
which hadoop (ensure hadoop is not present and not in the path)
tar -zxvf hadoop-2.0.3-alpha.tar.gz
HADOOP_CLIENT_OPTS='-agentlib:jdwp=transport=dt_socket,address=localhost:9009,server=y,suspend=y'
hadoop-2.0.3-alpha/bin/hadoop jar anything
{noformat}
Could you try the above and see if you see a different behavior?
From what I can see, the hadoop script calls hadoop-config.sh which in turn
calls hadoop-env.sh. Both the hadoop script and the hadoop-env.sh script
append the value of HADOOP_CLIENT_OPTS to HADOOP_OPTS.
HADOOP_CLIENT_OPTS is appended twice, causing JVM failures
--
Key: HADOOP-9455
URL: https://issues.apache.org/jira/browse/HADOOP-9455
Project: Hadoop Common
Issue Type: Bug
Components: bin
Affects Versions: 2.0.3-alpha
Reporter: Sangjin Lee
Priority: Minor
If you set HADOOP_CLIENT_OPTS and run hadoop, you'll find that the
HADOOP_CLIENT_OPTS value gets appended twice, and leads to JVM start failures
for cases like adding debug flags.
For example,
{noformat}
HADOOP_CLIENT_OPTS='-agentlib:jdwp=transport=dt_socket,address=localhost:9009,server=y,suspend=y'
hadoop jar anything
ERROR: Cannot load this JVM TI agent twice, check your java command line for
duplicate jdwp options.
Error occurred during initialization of VM
agent library failed to init: jdwp
{noformat}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HADOOP-8545) Filesystem Implementation for OpenStack Swift
[ https://issues.apache.org/jira/browse/HADOOP-8545?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Erik Bergenholtz updated HADOOP-8545: - Description: ,Add a filesystem implementation for OpenStack Swift object store, similar to the one which exists today for S3. (was: Add a filesystem implementation for OpenStack Swift object store, similar to the one which exists today for S3.) Filesystem Implementation for OpenStack Swift - Key: HADOOP-8545 URL: https://issues.apache.org/jira/browse/HADOOP-8545 Project: Hadoop Common Issue Type: New Feature Components: fs Affects Versions: 2.0.3-alpha, 1.1.2 Reporter: Tim Miller Assignee: Dmitry Mezhensky Labels: hadoop, patch Attachments: HADOOP-8545-10.patch, HADOOP-8545-11.patch, HADOOP-8545-12.patch, HADOOP-8545-13.patch, HADOOP-8545-14.patch, HADOOP-8545-15.patch, HADOOP-8545-16.patch, HADOOP-8545-17.patch, HADOOP-8545-18.patch, HADOOP-8545-19.patch, HADOOP-8545-1.patch, HADOOP-8545-20.patch, HADOOP-8545-2.patch, HADOOP-8545-3.patch, HADOOP-8545-4.patch, HADOOP-8545-5.patch, HADOOP-8545-6.patch, HADOOP-8545-7.patch, HADOOP-8545-8.patch, HADOOP-8545-9.patch, HADOOP-8545-javaclouds-2.patch, HADOOP-8545.patch, HADOOP-8545.patch ,Add a filesystem implementation for OpenStack Swift object store, similar to the one which exists today for S3. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HADOOP-9455) HADOOP_CLIENT_OPTS is appended twice, causing JVM failures
[
https://issues.apache.org/jira/browse/HADOOP-9455?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chris Nauroth updated HADOOP-9455:
--
Target Version/s: 3.0.0, 2.0.4-alpha
Affects Version/s: 3.0.0
Assignee: Chris Nauroth
HADOOP_CLIENT_OPTS is appended twice, causing JVM failures
--
Key: HADOOP-9455
URL: https://issues.apache.org/jira/browse/HADOOP-9455
Project: Hadoop Common
Issue Type: Bug
Components: bin
Affects Versions: 3.0.0, 2.0.3-alpha
Reporter: Sangjin Lee
Assignee: Chris Nauroth
Priority: Minor
If you set HADOOP_CLIENT_OPTS and run hadoop, you'll find that the
HADOOP_CLIENT_OPTS value gets appended twice, and leads to JVM start failures
for cases like adding debug flags.
For example,
{noformat}
HADOOP_CLIENT_OPTS='-agentlib:jdwp=transport=dt_socket,address=localhost:9009,server=y,suspend=y'
hadoop jar anything
ERROR: Cannot load this JVM TI agent twice, check your java command line for
duplicate jdwp options.
Error occurred during initialization of VM
agent library failed to init: jdwp
{noformat}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HADOOP-9455) HADOOP_CLIENT_OPTS is appended twice, causing JVM failures
[
https://issues.apache.org/jira/browse/HADOOP-9455?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chris Nauroth updated HADOOP-9455:
--
Attachment: HADOOP-9455.1.patch
Sangjin, thank you for the extra details. I can repro now. I tend to override
my hadoop-env.sh locally, so I didn't notice it at first.
I think we can remove the append of HADOOP_CLIENT_OPS from hadoop-env.sh,
considering that the main entry points all take care of appending it. The
hadoop script appends HADOOP_CLIENT_OPTS, the hdfs script appends
HADOOP_CLIENT_OPTS, and the yarn script appends YARN_CLIENT_OPTS. I'm
uploading a patch.
[~eli], you added this version of hadoop-env.sh in HADOOP-8287. Can I please
get your opinion on whether or not this patch is a safe change? Thanks!
HADOOP_CLIENT_OPTS is appended twice, causing JVM failures
--
Key: HADOOP-9455
URL: https://issues.apache.org/jira/browse/HADOOP-9455
Project: Hadoop Common
Issue Type: Bug
Components: bin
Affects Versions: 3.0.0, 2.0.3-alpha
Reporter: Sangjin Lee
Assignee: Chris Nauroth
Priority: Minor
Attachments: HADOOP-9455.1.patch
If you set HADOOP_CLIENT_OPTS and run hadoop, you'll find that the
HADOOP_CLIENT_OPTS value gets appended twice, and leads to JVM start failures
for cases like adding debug flags.
For example,
{noformat}
HADOOP_CLIENT_OPTS='-agentlib:jdwp=transport=dt_socket,address=localhost:9009,server=y,suspend=y'
hadoop jar anything
ERROR: Cannot load this JVM TI agent twice, check your java command line for
duplicate jdwp options.
Error occurred during initialization of VM
agent library failed to init: jdwp
{noformat}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HADOOP-9455) HADOOP_CLIENT_OPTS is appended twice, causing JVM failures
[
https://issues.apache.org/jira/browse/HADOOP-9455?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13626894#comment-13626894
]
Hadoop QA commented on HADOOP-9455:
---
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12577835/HADOOP-9455.1.patch
against trunk revision .
{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}. The javadoc tool did not generate any
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 1.3.9) 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-common.
{color:green}+1 contrib tests{color}. The patch passed contrib unit tests.
Test results:
https://builds.apache.org/job/PreCommit-HADOOP-Build/2432//testReport/
Console output:
https://builds.apache.org/job/PreCommit-HADOOP-Build/2432//console
This message is automatically generated.
HADOOP_CLIENT_OPTS is appended twice, causing JVM failures
--
Key: HADOOP-9455
URL: https://issues.apache.org/jira/browse/HADOOP-9455
Project: Hadoop Common
Issue Type: Bug
Components: bin
Affects Versions: 3.0.0, 2.0.3-alpha
Reporter: Sangjin Lee
Assignee: Chris Nauroth
Priority: Minor
Attachments: HADOOP-9455.1.patch
If you set HADOOP_CLIENT_OPTS and run hadoop, you'll find that the
HADOOP_CLIENT_OPTS value gets appended twice, and leads to JVM start failures
for cases like adding debug flags.
For example,
{noformat}
HADOOP_CLIENT_OPTS='-agentlib:jdwp=transport=dt_socket,address=localhost:9009,server=y,suspend=y'
hadoop jar anything
ERROR: Cannot load this JVM TI agent twice, check your java command line for
duplicate jdwp options.
Error occurred during initialization of VM
agent library failed to init: jdwp
{noformat}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HADOOP-9455) HADOOP_CLIENT_OPTS is appended twice, causing JVM failures
[
https://issues.apache.org/jira/browse/HADOOP-9455?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13626912#comment-13626912
]
Chris Nauroth commented on HADOOP-9455:
---
Jenkins reported no new tests, because the patch changes a shell script only.
HADOOP_CLIENT_OPTS is appended twice, causing JVM failures
--
Key: HADOOP-9455
URL: https://issues.apache.org/jira/browse/HADOOP-9455
Project: Hadoop Common
Issue Type: Bug
Components: bin
Affects Versions: 3.0.0, 2.0.3-alpha
Reporter: Sangjin Lee
Assignee: Chris Nauroth
Priority: Minor
Attachments: HADOOP-9455.1.patch
If you set HADOOP_CLIENT_OPTS and run hadoop, you'll find that the
HADOOP_CLIENT_OPTS value gets appended twice, and leads to JVM start failures
for cases like adding debug flags.
For example,
{noformat}
HADOOP_CLIENT_OPTS='-agentlib:jdwp=transport=dt_socket,address=localhost:9009,server=y,suspend=y'
hadoop jar anything
ERROR: Cannot load this JVM TI agent twice, check your java command line for
duplicate jdwp options.
Error occurred during initialization of VM
agent library failed to init: jdwp
{noformat}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HADOOP-6842) hadoop fs -text does not give a useful text representation of MapWritable objects
[
https://issues.apache.org/jira/browse/HADOOP-6842?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13626986#comment-13626986
]
Andrew Ash commented on HADOOP-6842:
Looks like nothing ever came of this? I'd appreciate a nicer toString() on
MapWritable too
hadoop fs -text does not give a useful text representation of MapWritable
objects
---
Key: HADOOP-6842
URL: https://issues.apache.org/jira/browse/HADOOP-6842
Project: Hadoop Common
Issue Type: Improvement
Affects Versions: 0.20.0
Reporter: Steven Wong
If a sequence file contains MapWritable objects, running hadoop fs -text on
the file prints the following for each MapWritable:
org.apache.hadoop.io.MapWritable@4f8235ed
To be more useful, it should print out the contents of the map instead. This
can be done by adding a toString method to MapWritable, i.e. something like:
public String toString() {
return (new TreeMapWritable, Writable(instance)).toString();
}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HADOOP-9455) HADOOP_CLIENT_OPTS is appended twice, causing JVM failures
[
https://issues.apache.org/jira/browse/HADOOP-9455?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13627001#comment-13627001
]
Eli Collins commented on HADOOP-9455:
-
Wouldn't it be better to only append HADOOP_CLIENT_OPTS once in hadoop-env.sh
rather than in each per-project bin script? Each can have a per-project
variable like Yarn if needed.
It looks like hadoop-config.sh handles the case where hadoop-env.sh doesn't
exist which is perhaps why all the bin scripts set it, but I don't think we
need to worry about hadoop-env.sh not existing post HADOOP-8287.
HADOOP_CLIENT_OPTS is appended twice, causing JVM failures
--
Key: HADOOP-9455
URL: https://issues.apache.org/jira/browse/HADOOP-9455
Project: Hadoop Common
Issue Type: Bug
Components: bin
Affects Versions: 3.0.0, 2.0.3-alpha
Reporter: Sangjin Lee
Assignee: Chris Nauroth
Priority: Minor
Attachments: HADOOP-9455.1.patch
If you set HADOOP_CLIENT_OPTS and run hadoop, you'll find that the
HADOOP_CLIENT_OPTS value gets appended twice, and leads to JVM start failures
for cases like adding debug flags.
For example,
{noformat}
HADOOP_CLIENT_OPTS='-agentlib:jdwp=transport=dt_socket,address=localhost:9009,server=y,suspend=y'
hadoop jar anything
ERROR: Cannot load this JVM TI agent twice, check your java command line for
duplicate jdwp options.
Error occurred during initialization of VM
agent library failed to init: jdwp
{noformat}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HADOOP-9464) In test*Conf.xml regexp replication factor set to 1
[
https://issues.apache.org/jira/browse/HADOOP-9464?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Anatoli Fomenko updated HADOOP-9464:
Attachment: HADOOP-9464.patch
The first version of the patch is attached. It brings the number of tests
failing on a Bigtop default cluster down to 96.
In test*Conf.xml regexp replication factor set to 1
---
Key: HADOOP-9464
URL: https://issues.apache.org/jira/browse/HADOOP-9464
Project: Hadoop Common
Issue Type: Bug
Components: test
Affects Versions: 2.0.4-alpha
Reporter: Anatoli Fomenko
Priority: Critical
Fix For: 2.0.4-alpha
Attachments: HADOOP-9464.patch
In some Hadoop smoke tests (testHDFSConf.xml), in expected output for
RegexpComparator, a replication factor is hard coded to 1,
{noformat}
test !-- TESTED --
descriptionls: file using absolute path/description
test-commands
command-fs NAMENODE -touchz /file1/command
command-fs NAMENODE -ls /file1/command
/test-commands
cleanup-commands
command-fs NAMENODE -rm /file1/command
/cleanup-commands
comparators
comparator
typeTokenComparator/type
expected-outputFound 1 items/expected-output
/comparator
comparator
typeRegexpComparator/type
expected-output^-rw-r--r--( )*1( )*[a-z]*( )*supergroup( )*0(
)*[0-9]{4,}-[0-9]{2,}-[0-9]{2,} [0-9]{2,}:[0-9]{2,}(
)*/file1/expected-output
/comparator
/comparators
/test
{noformat}
such as the first 1 in
{noformat}
expected-output^-rw-r--r--( )*1( )*[a-z]*( )*supergroup( )*0(
)*[0-9]{4,}-[0-9]{2,}-[0-9]{2,} [0-9]{2,}:[0-9]{2,}(
)*/file1/expected-output
{noformat}.
We found in Bigtop testing on a standalone cluster that such tests fail with
a default replication factor.
Please update the regexp in test*Conf.xml files to add a flexibility for a
replication factor that would allow to execute these tests with a variety of
clusters, or inside the Bigtop.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HADOOP-9307) BufferedFSInputStream.read returns wrong results after certain seeks
[ https://issues.apache.org/jira/browse/HADOOP-9307?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13627129#comment-13627129 ] Todd Lipcon commented on HADOOP-9307: - [~ste...@apache.org], mind taking a look? BufferedFSInputStream.read returns wrong results after certain seeks Key: HADOOP-9307 URL: https://issues.apache.org/jira/browse/HADOOP-9307 Project: Hadoop Common Issue Type: Bug Components: fs Affects Versions: 1.1.1, 2.0.2-alpha Reporter: Todd Lipcon Assignee: Todd Lipcon Attachments: hadoop-9307.txt After certain sequences of seek/read, BufferedFSInputStream can silently return data from the wrong part of the file. Further description in first comment below. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HADOOP-9463) branch-1-win fails to build with OpenJDK7
[ https://issues.apache.org/jira/browse/HADOOP-9463?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13627299#comment-13627299 ] Suresh Srinivas commented on HADOOP-9463: - Ivan, Jenkins cannot deal with the branch-1 patches. So there is no need to submit it. +1 for the patch. branch-1-win fails to build with OpenJDK7 - Key: HADOOP-9463 URL: https://issues.apache.org/jira/browse/HADOOP-9463 Project: Hadoop Common Issue Type: Bug Reporter: Ivan Mitic Assignee: Ivan Mitic Fix For: 1-win Attachments: HADOOP-9463.branch-1-win.jdk7.patch Build fails with the following error: I:\svn\trunk_rebase\hadoop-common [branch-1-win] ant clean winpkg Buildfile: I:\svn\trunk_rebase\hadoop-common\build.xml BUILD FAILED I:\svn\trunk_rebase\hadoop-common\build.xml:87: Unable to create javax script engine for javascript -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HADOOP-9463) branch-1-win fails to build with OpenJDK7
[ https://issues.apache.org/jira/browse/HADOOP-9463?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Suresh Srinivas updated HADOOP-9463: Resolution: Fixed Hadoop Flags: Reviewed Status: Resolved (was: Patch Available) I committed the change to branch-1-win. Thank you Ivan. branch-1-win fails to build with OpenJDK7 - Key: HADOOP-9463 URL: https://issues.apache.org/jira/browse/HADOOP-9463 Project: Hadoop Common Issue Type: Bug Reporter: Ivan Mitic Assignee: Ivan Mitic Fix For: 1-win Attachments: HADOOP-9463.branch-1-win.jdk7.patch Build fails with the following error: I:\svn\trunk_rebase\hadoop-common [branch-1-win] ant clean winpkg Buildfile: I:\svn\trunk_rebase\hadoop-common\build.xml BUILD FAILED I:\svn\trunk_rebase\hadoop-common\build.xml:87: Unable to create javax script engine for javascript -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HADOOP-9437) TestNativeIO#testRenameTo fails on Windows due to assumption that POSIX errno is embedded in NativeIOException
[
https://issues.apache.org/jira/browse/HADOOP-9437?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13627317#comment-13627317
]
Suresh Srinivas commented on HADOOP-9437:
-
+1 for the patch.
TestNativeIO#testRenameTo fails on Windows due to assumption that POSIX errno
is embedded in NativeIOException
--
Key: HADOOP-9437
URL: https://issues.apache.org/jira/browse/HADOOP-9437
Project: Hadoop Common
Issue Type: Bug
Components: test
Affects Versions: 3.0.0
Reporter: Chris Nauroth
Assignee: Chris Nauroth
Attachments: HADOOP-9437.1.patch, HADOOP-9437.2.patch,
HADOOP-9437.3.patch
HDFS-4428 added a detailed error message for failures to rename files by
embedding the POSIX errno in the {{NativeIOException}}. On Windows, the
mapping of errno is not performed, so the errno enum value will not be
present in the {{NativeIOException}}.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HADOOP-9437) TestNativeIO#testRenameTo fails on Windows due to assumption that POSIX errno is embedded in NativeIOException
[
https://issues.apache.org/jira/browse/HADOOP-9437?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Suresh Srinivas updated HADOOP-9437:
Resolution: Fixed
Fix Version/s: 3.0.0
Hadoop Flags: Reviewed
Status: Resolved (was: Patch Available)
I committed the patch to trunk. Thank you Chris.
Thank you Ivan for reviewing the patch.
TestNativeIO#testRenameTo fails on Windows due to assumption that POSIX errno
is embedded in NativeIOException
--
Key: HADOOP-9437
URL: https://issues.apache.org/jira/browse/HADOOP-9437
Project: Hadoop Common
Issue Type: Bug
Components: test
Affects Versions: 3.0.0
Reporter: Chris Nauroth
Assignee: Chris Nauroth
Fix For: 3.0.0
Attachments: HADOOP-9437.1.patch, HADOOP-9437.2.patch,
HADOOP-9437.3.patch
HDFS-4428 added a detailed error message for failures to rename files by
embedding the POSIX errno in the {{NativeIOException}}. On Windows, the
mapping of errno is not performed, so the errno enum value will not be
present in the {{NativeIOException}}.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HADOOP-9437) TestNativeIO#testRenameTo fails on Windows due to assumption that POSIX errno is embedded in NativeIOException
[
https://issues.apache.org/jira/browse/HADOOP-9437?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13627324#comment-13627324
]
Hudson commented on HADOOP-9437:
Integrated in Hadoop-trunk-Commit #3587 (See
[https://builds.apache.org/job/Hadoop-trunk-Commit/3587/])
HADOOP-9437. TestNativeIO#testRenameTo fails on Windows due to assumption
that POSIX errno is embedded in NativeIOException. Contributed by Chris
Nauroth. (Revision 1466306)
Result = SUCCESS
suresh : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVNview=revrev=1466306
Files :
* /hadoop/common/trunk/hadoop-common-project/hadoop-common/CHANGES.txt
*
/hadoop/common/trunk/hadoop-common-project/hadoop-common/src/main/native/src/org/apache/hadoop/io/nativeio/NativeIO.c
*
/hadoop/common/trunk/hadoop-common-project/hadoop-common/src/test/java/org/apache/hadoop/io/nativeio/TestNativeIO.java
TestNativeIO#testRenameTo fails on Windows due to assumption that POSIX errno
is embedded in NativeIOException
--
Key: HADOOP-9437
URL: https://issues.apache.org/jira/browse/HADOOP-9437
Project: Hadoop Common
Issue Type: Bug
Components: test
Affects Versions: 3.0.0
Reporter: Chris Nauroth
Assignee: Chris Nauroth
Fix For: 3.0.0
Attachments: HADOOP-9437.1.patch, HADOOP-9437.2.patch,
HADOOP-9437.3.patch
HDFS-4428 added a detailed error message for failures to rename files by
embedding the POSIX errno in the {{NativeIOException}}. On Windows, the
mapping of errno is not performed, so the errno enum value will not be
present in the {{NativeIOException}}.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HADOOP-9463) branch-1-win fails to build with OpenJDK7
[ https://issues.apache.org/jira/browse/HADOOP-9463?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13627337#comment-13627337 ] Ivan Mitic commented on HADOOP-9463: Thanks Suresh! bq. Jenkins cannot deal with the branch-1 patches. So there is no need to submit it. I wanted the Jira to show up as patch available. Will note this for the future patches, thanks. branch-1-win fails to build with OpenJDK7 - Key: HADOOP-9463 URL: https://issues.apache.org/jira/browse/HADOOP-9463 Project: Hadoop Common Issue Type: Bug Reporter: Ivan Mitic Assignee: Ivan Mitic Fix For: 1-win Attachments: HADOOP-9463.branch-1-win.jdk7.patch Build fails with the following error: I:\svn\trunk_rebase\hadoop-common [branch-1-win] ant clean winpkg Buildfile: I:\svn\trunk_rebase\hadoop-common\build.xml BUILD FAILED I:\svn\trunk_rebase\hadoop-common\build.xml:87: Unable to create javax script engine for javascript -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HADOOP-9452) Windows install scripts bugfixes
[ https://issues.apache.org/jira/browse/HADOOP-9452?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13627351#comment-13627351 ] Suresh Srinivas commented on HADOOP-9452: - bq. I noticed one thing that would be nice to improve in the patch – to nicely format the config file when new properties are added. Ivan, is the patch ready to be reviewed or does it still need more work? Windows install scripts bugfixes Key: HADOOP-9452 URL: https://issues.apache.org/jira/browse/HADOOP-9452 Project: Hadoop Common Issue Type: Bug Affects Versions: 1-win Reporter: Ivan Mitic Assignee: Ivan Mitic Attachments: HADOOP-9452.branch-1-win.installerfixes.patch A few bugfixes we've done to install scripts on Windows. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HADOOP-9452) Windows install scripts bugfixes
[ https://issues.apache.org/jira/browse/HADOOP-9452?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13627358#comment-13627358 ] Ivan Mitic commented on HADOOP-9452: Thanks for reviewing Suresh. I noticed one minor thing I'd like to improve in the patch before it is reviewed/committed, please hold for a bit. Windows install scripts bugfixes Key: HADOOP-9452 URL: https://issues.apache.org/jira/browse/HADOOP-9452 Project: Hadoop Common Issue Type: Bug Affects Versions: 1-win Reporter: Ivan Mitic Assignee: Ivan Mitic Attachments: HADOOP-9452.branch-1-win.installerfixes.patch A few bugfixes we've done to install scripts on Windows. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HADOOP-9443) Port winutils static code analysis change to trunk
[ https://issues.apache.org/jira/browse/HADOOP-9443?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13627447#comment-13627447 ] Ivan Mitic commented on HADOOP-9443: Thanks Chuan for the patch! I diffed with HADOOP-9177 and it looks good, +1 Btw, I think the general recommendation is to reactivate the existing Jira and post a patch compatible with a different branch instead of creating a new Jira. This makes it transparent to the reviewer/committer that the code has already been reviewed. Port winutils static code analysis change to trunk -- Key: HADOOP-9443 URL: https://issues.apache.org/jira/browse/HADOOP-9443 Project: Hadoop Common Issue Type: Bug Affects Versions: 3.0.0 Reporter: Chuan Liu Assignee: Chuan Liu Attachments: HADOOP-9443-trunk.patch We hit a problem in winutils when running tests on Windows. The static code analysis change will fix the problem. More specifically, the old code always assumes the security descriptor get from GetSecurityDescriptorControl() is relative, and will make an absolute security descriptor out of it. The new absolute security descriptor will then pass to SetSecurityDescriptorDacl() to set permissions on the file. If the security descriptor is absolute, the new absolute security descriptor will be NULL, and we will run into the problem. This is what happened exactly in our case. The fix from static code analysis will solve the problem. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (HADOOP-9467) Metrics2 record filtering (.record.filter.include/exclude) does not filter by name
Chris Nauroth created HADOOP-9467: - Summary: Metrics2 record filtering (.record.filter.include/exclude) does not filter by name Key: HADOOP-9467 URL: https://issues.apache.org/jira/browse/HADOOP-9467 Project: Hadoop Common Issue Type: Bug Components: metrics Affects Versions: 3.0.0, 1-win, 2.0.4-alpha Reporter: Chris Nauroth Assignee: Chris Nauroth Filtering by record considers only the record's tag for filtering and not the record's name. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HADOOP-9467) Metrics2 record filtering (.record.filter.include/exclude) does not filter by name
[ https://issues.apache.org/jira/browse/HADOOP-9467?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chris Nauroth updated HADOOP-9467: -- Target Version/s: 1.2.0, 3.0.0, 1-win, 2.0.4-alpha (was: 3.0.0, 1-win, 2.0.4-alpha) Affects Version/s: 1.2.0 Metrics2 record filtering (.record.filter.include/exclude) does not filter by name -- Key: HADOOP-9467 URL: https://issues.apache.org/jira/browse/HADOOP-9467 Project: Hadoop Common Issue Type: Bug Components: metrics Affects Versions: 1.2.0, 3.0.0, 1-win, 2.0.4-alpha Reporter: Chris Nauroth Assignee: Chris Nauroth Filtering by record considers only the record's tag for filtering and not the record's name. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HADOOP-9467) Metrics2 record filtering (.record.filter.include/exclude) does not filter by name
[ https://issues.apache.org/jira/browse/HADOOP-9467?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chris Nauroth updated HADOOP-9467: -- Attachment: HADOOP-9467-branch-1.1.patch Metrics2 record filtering (.record.filter.include/exclude) does not filter by name -- Key: HADOOP-9467 URL: https://issues.apache.org/jira/browse/HADOOP-9467 Project: Hadoop Common Issue Type: Bug Components: metrics Affects Versions: 1.2.0, 3.0.0, 1-win, 2.0.4-alpha Reporter: Chris Nauroth Assignee: Chris Nauroth Attachments: HADOOP-9467-branch-1.1.patch Filtering by record considers only the record's tag for filtering and not the record's name. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HADOOP-9467) Metrics2 record filtering (.record.filter.include/exclude) does not filter by name
[ https://issues.apache.org/jira/browse/HADOOP-9467?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chris Nauroth updated HADOOP-9467: -- Status: Patch Available (was: Open) Metrics2 record filtering (.record.filter.include/exclude) does not filter by name -- Key: HADOOP-9467 URL: https://issues.apache.org/jira/browse/HADOOP-9467 Project: Hadoop Common Issue Type: Bug Components: metrics Affects Versions: 1.2.0, 3.0.0, 1-win, 2.0.4-alpha Reporter: Chris Nauroth Assignee: Chris Nauroth Attachments: HADOOP-9467.1.patch, HADOOP-9467-branch-1.1.patch Filtering by record considers only the record's tag for filtering and not the record's name. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HADOOP-9467) Metrics2 record filtering (.record.filter.include/exclude) does not filter by name
[ https://issues.apache.org/jira/browse/HADOOP-9467?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chris Nauroth updated HADOOP-9467: -- Attachment: HADOOP-9467.1.patch This changes the filtering to consider both record name and tags. I've also added unit tests to cover these cases. I've attached patches for trunk and branch-1. Please commit the branch-1 patch to branch-1-win also. Credit for this patch should go to both me and Ganeshan Iyer. Thanks! Metrics2 record filtering (.record.filter.include/exclude) does not filter by name -- Key: HADOOP-9467 URL: https://issues.apache.org/jira/browse/HADOOP-9467 Project: Hadoop Common Issue Type: Bug Components: metrics Affects Versions: 1.2.0, 3.0.0, 1-win, 2.0.4-alpha Reporter: Chris Nauroth Assignee: Chris Nauroth Attachments: HADOOP-9467.1.patch, HADOOP-9467-branch-1.1.patch Filtering by record considers only the record's tag for filtering and not the record's name. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HADOOP-9467) Metrics2 record filtering (.record.filter.include/exclude) does not filter by name
[
https://issues.apache.org/jira/browse/HADOOP-9467?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13627513#comment-13627513
]
Hadoop QA commented on HADOOP-9467:
---
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12577955/HADOOP-9467.1.patch
against trunk revision .
{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}. The javadoc tool did not generate any
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 1.3.9) 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-common.
{color:green}+1 contrib tests{color}. The patch passed contrib unit tests.
Test results:
https://builds.apache.org/job/PreCommit-HADOOP-Build/2433//testReport/
Console output:
https://builds.apache.org/job/PreCommit-HADOOP-Build/2433//console
This message is automatically generated.
Metrics2 record filtering (.record.filter.include/exclude) does not filter by
name
--
Key: HADOOP-9467
URL: https://issues.apache.org/jira/browse/HADOOP-9467
Project: Hadoop Common
Issue Type: Bug
Components: metrics
Affects Versions: 1.2.0, 3.0.0, 1-win, 2.0.4-alpha
Reporter: Chris Nauroth
Assignee: Chris Nauroth
Attachments: HADOOP-9467.1.patch, HADOOP-9467-branch-1.1.patch
Filtering by record considers only the record's tag for filtering and not the
record's name.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
