[jira] [Commented] (HADOOP-10017) Fix NPE in DFSClient#getDelegationToken when doing Distcp from a secured cluster to an insecured cluster
[
https://issues.apache.org/jira/browse/HADOOP-10017?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13787503#comment-13787503
]
Hadoop QA commented on HADOOP-10017:
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12606858/HADOOP-10017.000.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-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/3182//testReport/
Console output:
https://builds.apache.org/job/PreCommit-HADOOP-Build/3182//console
This message is automatically generated.
Fix NPE in DFSClient#getDelegationToken when doing Distcp from a secured
cluster to an insecured cluster
Key: HADOOP-10017
URL: https://issues.apache.org/jira/browse/HADOOP-10017
Project: Hadoop Common
Issue Type: Sub-task
Affects Versions: 3.0.0, 2.1.1-beta
Reporter: Jing Zhao
Assignee: Haohui Mai
Attachments: HADOOP-10017.000.patch
Currently if we run Distcp from a secured cluster and copy data to an
insecured cluster, DFSClient#getDelegationToken will throw NPE when
processing the NULL token returned by the NN in the insecured cluster. We
should be able to handle the NULL token here.
--
This message was sent by Atlassian JIRA
(v6.1#6144)
[jira] [Commented] (HADOOP-10017) Fix NPE in DFSClient#getDelegationToken when doing Distcp from a secured cluster to an insecured cluster
[ https://issues.apache.org/jira/browse/HADOOP-10017?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13787506#comment-13787506 ] Jing Zhao commented on HADOOP-10017: +1. I will commit it shortly. Fix NPE in DFSClient#getDelegationToken when doing Distcp from a secured cluster to an insecured cluster Key: HADOOP-10017 URL: https://issues.apache.org/jira/browse/HADOOP-10017 Project: Hadoop Common Issue Type: Sub-task Affects Versions: 3.0.0, 2.1.1-beta Reporter: Jing Zhao Assignee: Haohui Mai Attachments: HADOOP-10017.000.patch Currently if we run Distcp from a secured cluster and copy data to an insecured cluster, DFSClient#getDelegationToken will throw NPE when processing the NULL token returned by the NN in the insecured cluster. We should be able to handle the NULL token here. -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Commented] (HADOOP-9984) FileSystem#globStatus and FileSystem#listStatus should resolve symlinks by default
[ https://issues.apache.org/jira/browse/HADOOP-9984?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13787507#comment-13787507 ] Suresh Srinivas commented on HADOOP-9984: - +1 on moving this to 2.3. [~cmccabe], can you comment? If I do not hear in a day or so, I will make this a blocker bug for 2.3. FileSystem#globStatus and FileSystem#listStatus should resolve symlinks by default -- Key: HADOOP-9984 URL: https://issues.apache.org/jira/browse/HADOOP-9984 Project: Hadoop Common Issue Type: Sub-task Components: fs Affects Versions: 2.1.0-beta Reporter: Colin Patrick McCabe Assignee: Colin Patrick McCabe Priority: Blocker Attachments: HADOOP-9984.001.patch, HADOOP-9984.003.patch, HADOOP-9984.005.patch, HADOOP-9984.007.patch, HADOOP-9984.009.patch, HADOOP-9984.010.patch, HADOOP-9984.011.patch, HADOOP-9984.012.patch, HADOOP-9984.013.patch, HADOOP-9984.014.patch, HADOOP-9984.015.patch During the process of adding symlink support to FileSystem, we realized that many existing HDFS clients would be broken by listStatus and globStatus returning symlinks. One example is applications that assume that !FileStatus#isFile implies that the inode is a directory. As we discussed in HADOOP-9972 and HADOOP-9912, we should default these APIs to returning resolved paths. -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Commented] (HADOOP-10017) Fix NPE in DFSClient#getDelegationToken when doing Distcp from a secured cluster to an insecured cluster
[ https://issues.apache.org/jira/browse/HADOOP-10017?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13787511#comment-13787511 ] Hudson commented on HADOOP-10017: - SUCCESS: Integrated in Hadoop-trunk-Commit #4552 (See [https://builds.apache.org/job/Hadoop-trunk-Commit/4552/]) HADOOP-10017. Fix NPE in DFSClient#getDelegationToken when doing Distcp from a secured cluster to an insecured cluster. Contributed by Haohui Mai. (jing9: http://svn.apache.org/viewcvs.cgi/?root=Apache-SVNview=revrev=1529571) * /hadoop/common/trunk/hadoop-common-project/hadoop-common/CHANGES.txt * /hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/DFSClient.java * /hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/test/java/org/apache/hadoop/hdfs/TestDistributedFileSystem.java Fix NPE in DFSClient#getDelegationToken when doing Distcp from a secured cluster to an insecured cluster Key: HADOOP-10017 URL: https://issues.apache.org/jira/browse/HADOOP-10017 Project: Hadoop Common Issue Type: Sub-task Affects Versions: 3.0.0, 2.1.1-beta Reporter: Jing Zhao Assignee: Haohui Mai Attachments: HADOOP-10017.000.patch Currently if we run Distcp from a secured cluster and copy data to an insecured cluster, DFSClient#getDelegationToken will throw NPE when processing the NULL token returned by the NN in the insecured cluster. We should be able to handle the NULL token here. -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Updated] (HADOOP-10017) Fix NPE in DFSClient#getDelegationToken when doing Distcp from a secured cluster to an insecured cluster
[ https://issues.apache.org/jira/browse/HADOOP-10017?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jing Zhao updated HADOOP-10017: --- Resolution: Fixed Fix Version/s: 2.1.2-beta Hadoop Flags: Reviewed Status: Resolved (was: Patch Available) I've committed this to trunk, branch-2 and branch-2.1-beta. Fix NPE in DFSClient#getDelegationToken when doing Distcp from a secured cluster to an insecured cluster Key: HADOOP-10017 URL: https://issues.apache.org/jira/browse/HADOOP-10017 Project: Hadoop Common Issue Type: Sub-task Affects Versions: 3.0.0, 2.1.1-beta Reporter: Jing Zhao Assignee: Haohui Mai Fix For: 2.1.2-beta Attachments: HADOOP-10017.000.patch Currently if we run Distcp from a secured cluster and copy data to an insecured cluster, DFSClient#getDelegationToken will throw NPE when processing the NULL token returned by the NN in the insecured cluster. We should be able to handle the NULL token here. -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Commented] (HADOOP-10017) Fix NPE in DFSClient#getDelegationToken when doing Distcp from a secured cluster to an insecured cluster
[ https://issues.apache.org/jira/browse/HADOOP-10017?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13787560#comment-13787560 ] Hudson commented on HADOOP-10017: - SUCCESS: Integrated in Hadoop-Yarn-trunk #354 (See [https://builds.apache.org/job/Hadoop-Yarn-trunk/354/]) HADOOP-10017. Fix NPE in DFSClient#getDelegationToken when doing Distcp from a secured cluster to an insecured cluster. Contributed by Haohui Mai. (jing9: http://svn.apache.org/viewcvs.cgi/?root=Apache-SVNview=revrev=1529571) * /hadoop/common/trunk/hadoop-common-project/hadoop-common/CHANGES.txt * /hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/DFSClient.java * /hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/test/java/org/apache/hadoop/hdfs/TestDistributedFileSystem.java Fix NPE in DFSClient#getDelegationToken when doing Distcp from a secured cluster to an insecured cluster Key: HADOOP-10017 URL: https://issues.apache.org/jira/browse/HADOOP-10017 Project: Hadoop Common Issue Type: Sub-task Affects Versions: 3.0.0, 2.1.1-beta Reporter: Jing Zhao Assignee: Haohui Mai Fix For: 2.1.2-beta Attachments: HADOOP-10017.000.patch Currently if we run Distcp from a secured cluster and copy data to an insecured cluster, DFSClient#getDelegationToken will throw NPE when processing the NULL token returned by the NN in the insecured cluster. We should be able to handle the NULL token here. -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Commented] (HADOOP-10017) Fix NPE in DFSClient#getDelegationToken when doing Distcp from a secured cluster to an insecured cluster
[ https://issues.apache.org/jira/browse/HADOOP-10017?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13787592#comment-13787592 ] Hudson commented on HADOOP-10017: - FAILURE: Integrated in Hadoop-Hdfs-trunk #1544 (See [https://builds.apache.org/job/Hadoop-Hdfs-trunk/1544/]) HADOOP-10017. Fix NPE in DFSClient#getDelegationToken when doing Distcp from a secured cluster to an insecured cluster. Contributed by Haohui Mai. (jing9: http://svn.apache.org/viewcvs.cgi/?root=Apache-SVNview=revrev=1529571) * /hadoop/common/trunk/hadoop-common-project/hadoop-common/CHANGES.txt * /hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/DFSClient.java * /hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/test/java/org/apache/hadoop/hdfs/TestDistributedFileSystem.java Fix NPE in DFSClient#getDelegationToken when doing Distcp from a secured cluster to an insecured cluster Key: HADOOP-10017 URL: https://issues.apache.org/jira/browse/HADOOP-10017 Project: Hadoop Common Issue Type: Sub-task Affects Versions: 3.0.0, 2.1.1-beta Reporter: Jing Zhao Assignee: Haohui Mai Fix For: 2.1.2-beta Attachments: HADOOP-10017.000.patch Currently if we run Distcp from a secured cluster and copy data to an insecured cluster, DFSClient#getDelegationToken will throw NPE when processing the NULL token returned by the NN in the insecured cluster. We should be able to handle the NULL token here. -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Commented] (HADOOP-10017) Fix NPE in DFSClient#getDelegationToken when doing Distcp from a secured cluster to an insecured cluster
[ https://issues.apache.org/jira/browse/HADOOP-10017?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13787607#comment-13787607 ] Hudson commented on HADOOP-10017: - FAILURE: Integrated in Hadoop-Mapreduce-trunk #1570 (See [https://builds.apache.org/job/Hadoop-Mapreduce-trunk/1570/]) HADOOP-10017. Fix NPE in DFSClient#getDelegationToken when doing Distcp from a secured cluster to an insecured cluster. Contributed by Haohui Mai. (jing9: http://svn.apache.org/viewcvs.cgi/?root=Apache-SVNview=revrev=1529571) * /hadoop/common/trunk/hadoop-common-project/hadoop-common/CHANGES.txt * /hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/DFSClient.java * /hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/test/java/org/apache/hadoop/hdfs/TestDistributedFileSystem.java Fix NPE in DFSClient#getDelegationToken when doing Distcp from a secured cluster to an insecured cluster Key: HADOOP-10017 URL: https://issues.apache.org/jira/browse/HADOOP-10017 Project: Hadoop Common Issue Type: Sub-task Affects Versions: 3.0.0, 2.1.1-beta Reporter: Jing Zhao Assignee: Haohui Mai Fix For: 2.1.2-beta Attachments: HADOOP-10017.000.patch Currently if we run Distcp from a secured cluster and copy data to an insecured cluster, DFSClient#getDelegationToken will throw NPE when processing the NULL token returned by the NN in the insecured cluster. We should be able to handle the NULL token here. -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Updated] (HADOOP-10020) disable symlinks temporarily
[ https://issues.apache.org/jira/browse/HADOOP-10020?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sanjay Radia updated HADOOP-10020: -- Attachment: Hadoop-10020-3.patch disable symlinks temporarily Key: HADOOP-10020 URL: https://issues.apache.org/jira/browse/HADOOP-10020 Project: Hadoop Common Issue Type: Sub-task Components: fs Affects Versions: 2.1.2-beta Reporter: Colin Patrick McCabe Assignee: Sanjay Radia Priority: Blocker Attachments: Hadoop-10020-2.patch, Hadoop-10020-3.patch, Hadoop-10020.patch disable symlinks temporarily until we can make them production-ready in Hadoop 2.3 -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Commented] (HADOOP-10022) Add support for per project https support
[ https://issues.apache.org/jira/browse/HADOOP-10022?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13787733#comment-13787733 ] Hudson commented on HADOOP-10022: - SUCCESS: Integrated in Hadoop-trunk-Commit #4554 (See [https://builds.apache.org/job/Hadoop-trunk-Commit/4554/]) YARN-1277. Added a policy based configuration for http/https in common HttpServer and using the same in YARN - related to per project https config support via HADOOP-10022. Contributed by Suresh Srinivas and Omkar Vinit Joshi. (vinodkv: http://svn.apache.org/viewcvs.cgi/?root=Apache-SVNview=revrev=1529662) * /hadoop/common/trunk/hadoop-common-project/hadoop-common/src/main/java/org/apache/hadoop/fs/CommonConfigurationKeysPublic.java * /hadoop/common/trunk/hadoop-common-project/hadoop-common/src/main/java/org/apache/hadoop/http/HttpConfig.java * /hadoop/common/trunk/hadoop-common-project/hadoop-common/src/test/java/org/apache/hadoop/http/TestSSLHttpServer.java * /hadoop/common/trunk/hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-app/src/main/java/org/apache/hadoop/mapreduce/v2/app/MRAppMaster.java * /hadoop/common/trunk/hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-app/src/main/java/org/apache/hadoop/mapreduce/v2/app/webapp/AppController.java * /hadoop/common/trunk/hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-common/src/main/java/org/apache/hadoop/mapreduce/v2/jobhistory/JHAdminConfig.java * /hadoop/common/trunk/hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-common/src/main/java/org/apache/hadoop/mapreduce/v2/util/MRWebAppUtil.java * /hadoop/common/trunk/hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-core/src/main/java/org/apache/hadoop/mapreduce/MRConfig.java * /hadoop/common/trunk/hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-core/src/main/resources/mapred-default.xml * /hadoop/common/trunk/hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-hs/src/main/java/org/apache/hadoop/mapreduce/v2/hs/JobHistoryServer.java * /hadoop/common/trunk/hadoop-yarn-project/CHANGES.txt * /hadoop/common/trunk/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-api/src/main/java/org/apache/hadoop/yarn/conf/YarnConfiguration.java * /hadoop/common/trunk/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-common/src/main/java/org/apache/hadoop/yarn/webapp/util/WebAppUtils.java * /hadoop/common/trunk/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-common/src/main/resources/yarn-default.xml * /hadoop/common/trunk/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-nodemanager/src/main/java/org/apache/hadoop/yarn/server/nodemanager/NodeManager.java * /hadoop/common/trunk/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/main/java/org/apache/hadoop/yarn/server/resourcemanager/ResourceManager.java * /hadoop/common/trunk/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-web-proxy/src/main/java/org/apache/hadoop/yarn/server/webproxy/ProxyUriUtils.java Add support for per project https support - Key: HADOOP-10022 URL: https://issues.apache.org/jira/browse/HADOOP-10022 Project: Hadoop Common Issue Type: Bug Reporter: Suresh Srinivas Priority: Blocker Current configuration hadoop.https.enable turns on https only support for all the daemons in hadoop. This is an umbrella jira to add per project https configuration. For more details, see the detailed proposal - https://issues.apache.org/jira/browse/HADOOP-8581?focusedCommentId=13784332page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-13784332 The current scope of work is described in - https://issues.apache.org/jira/browse/HADOOP-8581?focusedCommentId=13786567page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-13786567 -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Resolved] (HADOOP-10022) Add support for per project https support
[ https://issues.apache.org/jira/browse/HADOOP-10022?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arun C Murthy resolved HADOOP-10022. Resolution: Fixed All subtasks are done. Add support for per project https support - Key: HADOOP-10022 URL: https://issues.apache.org/jira/browse/HADOOP-10022 Project: Hadoop Common Issue Type: Bug Reporter: Suresh Srinivas Priority: Blocker Current configuration hadoop.https.enable turns on https only support for all the daemons in hadoop. This is an umbrella jira to add per project https configuration. For more details, see the detailed proposal - https://issues.apache.org/jira/browse/HADOOP-8581?focusedCommentId=13784332page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-13784332 The current scope of work is described in - https://issues.apache.org/jira/browse/HADOOP-8581?focusedCommentId=13786567page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-13786567 -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Commented] (HADOOP-10026) Upgrade to Jackson 2
[ https://issues.apache.org/jira/browse/HADOOP-10026?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13787744#comment-13787744 ] Steve Loughran commented on HADOOP-10026: - # the jenkins complaint is because the patch has to start at trunk -can you recreate it from there? # Why upgrade? What benefits does it bring? What is the price of not upgrading? # what is the minimum version of jackson needed for the new API hadoop-openstack isn't shipping yet, so changes there may not be as dangerous. It uses JSON in two places: auth and directory listings. For Auth we don't care about performance, though we do care about authenticating with different openstack implementations, so the new API would need to be tested against: rackspace US, UK, and HP cloud, leaving rackspace other openstack developers (such as Mirantis) to test against the pre-release stuff. It proved surprisingly brittle and I'd be very reluctant to change it unless it was particularly compelling. Upgrade to Jackson 2 Key: HADOOP-10026 URL: https://issues.apache.org/jira/browse/HADOOP-10026 Project: Hadoop Common Issue Type: Task Reporter: Ben McCann Attachments: hadoop-tools-openstack-jackson.patch I'd like to see Hadoop upgrade to Jackson 2. This is a change that should be able to be made to each Hadoop project one at a time, so I've attached a patch for the first and will follow up with others if this one is committed. -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Commented] (HADOOP-10020) disable symlinks temporarily
[
https://issues.apache.org/jira/browse/HADOOP-10020?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13787748#comment-13787748
]
Hadoop QA commented on HADOOP-10020:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12607091/Hadoop-10020-3.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/3184//console
This message is automatically generated.
disable symlinks temporarily
Key: HADOOP-10020
URL: https://issues.apache.org/jira/browse/HADOOP-10020
Project: Hadoop Common
Issue Type: Sub-task
Components: fs
Affects Versions: 2.1.2-beta
Reporter: Colin Patrick McCabe
Assignee: Sanjay Radia
Priority: Blocker
Attachments: Hadoop-10020-2.patch, Hadoop-10020-3.patch,
Hadoop-10020.patch
disable symlinks temporarily until we can make them production-ready in
Hadoop 2.3
--
This message was sent by Atlassian JIRA
(v6.1#6144)
[jira] [Commented] (HADOOP-10026) Upgrade to Jackson 2
[ https://issues.apache.org/jira/browse/HADOOP-10026?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13787749#comment-13787749 ] Ben McCann commented on HADOOP-10026: - I'm confused by what you mean when you say the patch has to start at trunk because I thought it did already. I used the svn checkout command on http://wiki.apache.org/hadoop/HowToContribute: svn checkout http://svn.apache.org/repos/asf/hadoop/common/trunk/ hadoop-trunk Upgrade to Jackson 2 Key: HADOOP-10026 URL: https://issues.apache.org/jira/browse/HADOOP-10026 Project: Hadoop Common Issue Type: Task Reporter: Ben McCann Attachments: hadoop-tools-openstack-jackson.patch I'd like to see Hadoop upgrade to Jackson 2. This is a change that should be able to be made to each Hadoop project one at a time, so I've attached a patch for the first and will follow up with others if this one is committed. -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Commented] (HADOOP-10020) disable symlinks temporarily
[
https://issues.apache.org/jira/browse/HADOOP-10020?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13787756#comment-13787756
]
Hadoop QA commented on HADOOP-10020:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12607091/Hadoop-10020-3.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/3185//console
This message is automatically generated.
disable symlinks temporarily
Key: HADOOP-10020
URL: https://issues.apache.org/jira/browse/HADOOP-10020
Project: Hadoop Common
Issue Type: Sub-task
Components: fs
Affects Versions: 2.1.2-beta
Reporter: Colin Patrick McCabe
Assignee: Sanjay Radia
Priority: Blocker
Attachments: Hadoop-10020-2.patch, Hadoop-10020-3.patch,
Hadoop-10020.patch
disable symlinks temporarily until we can make them production-ready in
Hadoop 2.3
--
This message was sent by Atlassian JIRA
(v6.1#6144)
[jira] [Updated] (HADOOP-10020) disable symlinks temporarily
[ https://issues.apache.org/jira/browse/HADOOP-10020?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sanjay Radia updated HADOOP-10020: -- Attachment: Hadoop-10020-4.patch Update patch against latest trunk disable symlinks temporarily Key: HADOOP-10020 URL: https://issues.apache.org/jira/browse/HADOOP-10020 Project: Hadoop Common Issue Type: Sub-task Components: fs Affects Versions: 2.1.2-beta Reporter: Colin Patrick McCabe Assignee: Sanjay Radia Priority: Blocker Attachments: Hadoop-10020-2.patch, Hadoop-10020-3.patch, Hadoop-10020-4.patch, Hadoop-10020.patch disable symlinks temporarily until we can make them production-ready in Hadoop 2.3 -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Commented] (HADOOP-10020) disable symlinks temporarily
[
https://issues.apache.org/jira/browse/HADOOP-10020?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13787761#comment-13787761
]
Hadoop QA commented on HADOOP-10020:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12607091/Hadoop-10020-3.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 2 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:red}-1 core tests{color}. The patch failed these unit tests in
hadoop-common-project/hadoop-common hadoop-hdfs-project/hadoop-hdfs:
org.apache.hadoop.hdfs.server.namenode.ha.TestRetryCacheWithHA
{color:green}+1 contrib tests{color}. The patch passed contrib unit tests.
Test results:
https://builds.apache.org/job/PreCommit-HADOOP-Build/3183//testReport/
Console output:
https://builds.apache.org/job/PreCommit-HADOOP-Build/3183//console
This message is automatically generated.
disable symlinks temporarily
Key: HADOOP-10020
URL: https://issues.apache.org/jira/browse/HADOOP-10020
Project: Hadoop Common
Issue Type: Sub-task
Components: fs
Affects Versions: 2.1.2-beta
Reporter: Colin Patrick McCabe
Assignee: Sanjay Radia
Priority: Blocker
Attachments: Hadoop-10020-2.patch, Hadoop-10020-3.patch,
Hadoop-10020-4.patch, Hadoop-10020.patch
disable symlinks temporarily until we can make them production-ready in
Hadoop 2.3
--
This message was sent by Atlassian JIRA
(v6.1#6144)
[jira] [Commented] (HADOOP-10020) disable symlinks temporarily
[ https://issues.apache.org/jira/browse/HADOOP-10020?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13787816#comment-13787816 ] Sanjay Radia commented on HADOOP-10020: --- As noted by chris, the TestRetryCacheWithHA is not related to this patch; further TestRetryCacheWithHA passed on my desktop. disable symlinks temporarily Key: HADOOP-10020 URL: https://issues.apache.org/jira/browse/HADOOP-10020 Project: Hadoop Common Issue Type: Sub-task Components: fs Affects Versions: 2.1.2-beta Reporter: Colin Patrick McCabe Assignee: Sanjay Radia Priority: Blocker Attachments: Hadoop-10020-2.patch, Hadoop-10020-3.patch, Hadoop-10020-4-forBranch2.1beta.patch, Hadoop-10020-4.patch, Hadoop-10020.patch disable symlinks temporarily until we can make them production-ready in Hadoop 2.3 -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Updated] (HADOOP-10020) disable symlinks temporarily
[ https://issues.apache.org/jira/browse/HADOOP-10020?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sanjay Radia updated HADOOP-10020: -- Status: Open (was: Patch Available) disable symlinks temporarily Key: HADOOP-10020 URL: https://issues.apache.org/jira/browse/HADOOP-10020 Project: Hadoop Common Issue Type: Sub-task Components: fs Affects Versions: 2.1.2-beta Reporter: Colin Patrick McCabe Assignee: Sanjay Radia Priority: Blocker Attachments: Hadoop-10020-2.patch, Hadoop-10020-3.patch, Hadoop-10020-4-forBranch2.1beta.patch, Hadoop-10020-4.patch, Hadoop-10020.patch disable symlinks temporarily until we can make them production-ready in Hadoop 2.3 -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Updated] (HADOOP-10020) disable symlinks temporarily
[ https://issues.apache.org/jira/browse/HADOOP-10020?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sanjay Radia updated HADOOP-10020: -- Attachment: Hadoop-10020-4-forBranch2.1beta.patch backported patch to branch-2.1beta. Main change is that RawLocalFileSystem does not have createSymlink. disable symlinks temporarily Key: HADOOP-10020 URL: https://issues.apache.org/jira/browse/HADOOP-10020 Project: Hadoop Common Issue Type: Sub-task Components: fs Affects Versions: 2.1.2-beta Reporter: Colin Patrick McCabe Assignee: Sanjay Radia Priority: Blocker Attachments: Hadoop-10020-2.patch, Hadoop-10020-3.patch, Hadoop-10020-4-forBranch2.1beta.patch, Hadoop-10020-4.patch, Hadoop-10020.patch disable symlinks temporarily until we can make them production-ready in Hadoop 2.3 -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Updated] (HADOOP-10020) disable symlinks temporarily
[ https://issues.apache.org/jira/browse/HADOOP-10020?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Suresh Srinivas updated HADOOP-10020: - Hadoop Flags: Incompatible change,Reviewed (was: Reviewed) Marking this as incompatible change. disable symlinks temporarily Key: HADOOP-10020 URL: https://issues.apache.org/jira/browse/HADOOP-10020 Project: Hadoop Common Issue Type: Sub-task Components: fs Affects Versions: 2.1.2-beta Reporter: Colin Patrick McCabe Assignee: Sanjay Radia Priority: Blocker Attachments: Hadoop-10020-2.patch, Hadoop-10020-3.patch, Hadoop-10020-4-forBranch2.1beta.patch, Hadoop-10020-4.patch, Hadoop-10020.patch disable symlinks temporarily until we can make them production-ready in Hadoop 2.3 -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Resolved] (HADOOP-10020) disable symlinks temporarily
[ https://issues.apache.org/jira/browse/HADOOP-10020?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Suresh Srinivas resolved HADOOP-10020. -- Resolution: Fixed Fix Version/s: 2.1.2-beta Release Note: During review of symbolic links, many issues were found related impact on semantics of existing APIs such FileSystem#listStatus, FileSystem#globStatus etc. There were also many issues brought up about symbolic links and the impact on security and functionality of HDFS. All these issues will be address in the upcoming release 2.3. Until then the feature is temporarily disabled. I have committed this change to 2.1-beta branch. disable symlinks temporarily Key: HADOOP-10020 URL: https://issues.apache.org/jira/browse/HADOOP-10020 Project: Hadoop Common Issue Type: Sub-task Components: fs Affects Versions: 2.1.2-beta Reporter: Colin Patrick McCabe Assignee: Sanjay Radia Priority: Blocker Fix For: 2.1.2-beta Attachments: Hadoop-10020-2.patch, Hadoop-10020-3.patch, Hadoop-10020-4-forBranch2.1beta.patch, Hadoop-10020-4.patch, Hadoop-10020.patch disable symlinks temporarily until we can make them production-ready in Hadoop 2.3 -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Updated] (HADOOP-9984) FileSystem#globStatus and FileSystem#listStatus should resolve symlinks by default
[ https://issues.apache.org/jira/browse/HADOOP-9984?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sanjay Radia updated HADOOP-9984: - Target Version/s: 2.3.0 (was: 2.1.2-beta) Making this a blocker on 2.3 and removing the blocker on 2.1.2-beta since Hadoop-10020 (disabling symlinks) has been committed to branch-2.1-beta. FileSystem#globStatus and FileSystem#listStatus should resolve symlinks by default -- Key: HADOOP-9984 URL: https://issues.apache.org/jira/browse/HADOOP-9984 Project: Hadoop Common Issue Type: Sub-task Components: fs Affects Versions: 2.1.0-beta Reporter: Colin Patrick McCabe Assignee: Colin Patrick McCabe Priority: Blocker Attachments: HADOOP-9984.001.patch, HADOOP-9984.003.patch, HADOOP-9984.005.patch, HADOOP-9984.007.patch, HADOOP-9984.009.patch, HADOOP-9984.010.patch, HADOOP-9984.011.patch, HADOOP-9984.012.patch, HADOOP-9984.013.patch, HADOOP-9984.014.patch, HADOOP-9984.015.patch During the process of adding symlink support to FileSystem, we realized that many existing HDFS clients would be broken by listStatus and globStatus returning symlinks. One example is applications that assume that !FileStatus#isFile implies that the inode is a directory. As we discussed in HADOOP-9972 and HADOOP-9912, we should default these APIs to returning resolved paths. -- This message was sent by Atlassian JIRA (v6.1#6144)
