[
https://issues.apache.org/jira/browse/HADOOP-3307?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12593082#action_12593082
]
Doug Cutting commented on HADOOP-3307:
--------------------------------------
> We would need mounts to make it transparent and some storage in the
> filesystem to know what we are supposed to do with the mounts.
Perhaps. But we don't want to go there in this issue, right?
> I was trying to get rid of the implicit assumption. [ ... ]
The assumption that an archive directory name end with ".har"? Is that what
troubles you?
Here's another option: use percent-encoding to name the archive dir in the
authority, e.g., har://hdfs:%2F%2Fhost:port%2Fdir%2Farchive/a/b. This is
harder to read, but otherwise elegant and general.
Or yet another option: use the name of a file *within* the archive directory,
like the index or parts which will also presumably be fixed, not user-variable.
Then a path might look something like
har://hdfs-host:port/dir/archive/har.index/a/b, where "har.index" is hardwired.
> 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.
