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

Suresh Srinivas updated HADOOP-10029:
-------------------------------------

    Attachment: HADOOP-10029.3.patch

bq. I would make ALL the copyFromXX and moveFromXX variants throw the exception 
rather than rely on the fact that FileSystem's default implementation calls one 
of copyFromXX that HarFileSystem implements and throws exception.
There are many other methods that rely on this such as create(), 
createNonRecursive() etc. We will be adding all these implementations. At some 
point in time, we should make the internal method used in FileSystem 
implementation of xyz() as xyzInternal() to establish this pattern.

bq. resolvePath(). Not sure what is correct here....
I am just restoring the previous behavior here (which was changed by 
HADOOP-10003). I will create a separate jira to discuss and address this.

Other comments taken care of.

> Specifying har file to MR job fails in secure cluster
> -----------------------------------------------------
>
>                 Key: HADOOP-10029
>                 URL: https://issues.apache.org/jira/browse/HADOOP-10029
>             Project: Hadoop Common
>          Issue Type: Bug
>          Components: fs
>            Reporter: Suresh Srinivas
>            Assignee: Suresh Srinivas
>             Fix For: 2.2.0
>
>         Attachments: HADOOP-10029.1.patch, HADOOP-10029.2.patch, 
> HADOOP-10029.3.patch, HADOOP-10029.patch
>
>
> This is an issue found by [~rramya]. See the exception stack trace in the 
> following comment.



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

Reply via email to