hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andrew Wang (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HADOOP-10052) Temporarily disable client-side symlink resolution
Date Thu, 17 Oct 2013 02:11:43 GMT

    [ https://issues.apache.org/jira/browse/HADOOP-10052?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13797540#comment-13797540

Andrew Wang commented on HADOOP-10052:

We've used "default disable" as a way of saying a feature isn't ready for prime-time before
(essentially, buyer beware). Since I think this JIRA is about client compatibility rather
than security or data loss, I think this suffices.

I don't feel that strongly though, and can whip up a patch using the branch-2.2 disable if
you prefer. One caveat is that we can't easily run jenkins against it since it's not in trunk.

> 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
>         Attachments: hadoop-10052-1.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

View raw message