[
https://issues.apache.org/jira/browse/HADOOP-3307?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12592551#action_12592551
]
Doug Cutting commented on HADOOP-3307:
--------------------------------------
> In har://hdfs-host:port/dir/foo.har/bar.har/file, what is the behavior if
> foo.har is indeed a directory and bar.har is an archive?
As I said before, I think it would be nice and not too difficult to make nested
archives work. Not essential, but convenient if its not too difficult. So if
you have hdfs://h:p/bar/* and you pack it into hdfs://foo/bar.har, then you
pack that into hdfs://h:p/foo/* into hdfs://h:p/dir/foo.har, then
har://hdfs-h:p/dir/foo.har/bar.har/file should either (a) contain the content
of the original file if we implement nested archives, or (b) throw
FileNotFoundException if we don't implement nested archives. Is that what you
were asking?
> Can we distinguish a directory ending with .har to be an archive only if it
> has index file in it.
If a path component of a har: uri ends with ".har" then I think it should be an
error if it is not a ".har" format directory. It's fine to have files named
.har in HDFS that are not har-format, but if one tries to access them using the
archive mechanism, we shouldn't silently ignore them, but rather throw a
MalformedArchive exception, no?
> 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.
