Mailing-List: contact common-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: common-issues@hadoop.apache.org
Date: Mon, 21 Oct 2013 17:56:43 +0000 (UTC)
From: "Andrew Wang (JIRA)" <jira@apache.org>
To: common-issues@hadoop.apache.org
Message-ID: <JIRA.12674157.1381944405923.98599.1382378203038@arcas>
In-Reply-To: <JIRA.12674157.1381944405923@arcas>
References: <JIRA.12674157.1381944405923@arcas>
Subject: [jira] [Reopened] (HADOOP-10052) Temporarily disable client-side
 symlink resolution
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/HADOOP-10052?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Andrew Wang reopened HADOOP-10052:
----------------------------------


Re-opening because our internal Jenkins revealed that I missed re-enabling symlinks in a test. Will post an addendum fix shortly.

> Temporarily disable client-side symlink resolution
> --------------------------------------------------
>
>                 Key: HADOOP-10052
>                 URL: https://issues.apache.org/jira/browse/HADOOP-10052
>             Project: Hadoop Common
>          Issue Type: Sub-task
>          Components: fs
>    Affects Versions: 2.2.0
>            Reporter: Andrew Wang
>            Assignee: Andrew Wang
>             Fix For: 2.2.1
>
>         Attachments: hadoop-10052-1.patch, hadoop-10052-branch-2.2-1.patch, hadoop-10052-branch-2-2-addendum.patch
>
>
> As a follow-on to the JIRA that disabled creation of symlinks on the server-side, we should also disable client-side resolution so old clients talking to a new server behave properly.


--
This message was sent by Atlassian JIRA
(v6.1#6144)