Mailing-List: contact core-dev-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: core-dev@hadoop.apache.org
Message-ID: <1024715266.1209157195766.JavaMail.jira@brutus>
Date: Fri, 25 Apr 2008 13:59:55 -0700 (PDT)
From: "Tsz Wo (Nicholas), SZE (JIRA)" <jira@apache.org>
To: core-dev@hadoop.apache.org
Subject: [jira] Commented: (HADOOP-3307) Archives in Hadoop.
In-Reply-To: <2035898356.1209069084690.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Tsz Wo (Nicholas), SZE commented on HADOOP-3307:
------------------------------------------------

> we assume any directory ending with .har is a an archive and the path following it is the path in archive.

Consider har://hdfs-host:port/dir/my.har/file/in/har.  I think the assumption should be
* if my.har is a file, then follow the path in archive.
* if my.har is a directory, treat it as a normal directory.

*Questions*: Do we support nested archive?  What will you do for something like har://hdfs-host:port/dir/foo.har/bar.har/file?


> Archives in Hadoop.
> -------------------
>
>                 Key: HADOOP-3307
>                 URL: https://issues.apache.org/jira/browse/HADOOP-3307
>             Project: Hadoop Core
>          Issue Type: New Feature
>          Components: fs
>            Reporter: Mahadev konar
>            Assignee: Mahadev konar
>             Fix For: 0.18.0
>
>
> This is a new feature for archiving and unarchiving files in HDFS. 

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.