[
https://issues.apache.org/jira/browse/HADOOP-3663?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12632433#action_12632433
]
Hairong Kuang commented on HADOOP-3663:
---------------------------------------
My point is that those paths not belonging to the archive should not be there
in the first place. Then there is no need to filter them later. Although there
are only a few lines, they made me to wonder why they are there and had to talk
to you to understand them. I do not think the fix needs a lot of time , why
complaining about bandwidth?
> Allow relative paths to be created inside archives.
> ---------------------------------------------------
>
> Key: HADOOP-3663
> URL: https://issues.apache.org/jira/browse/HADOOP-3663
> Project: Hadoop Core
> Issue Type: Improvement
> Components: tools/harchive
> Affects Versions: 0.18.0
> Reporter: Mahadev konar
> Assignee: Mahadev konar
> Fix For: 0.19.0
>
> Attachments: HADOOP-3663.patch, HADOOP-3663.patch, HADOOP-3663.patch
>
>
> Archives currently stores the full path from the input sources -- since it
> allows multiple sources and regular expressions as inputs. So the created
> archives have the full path of the input sources. This is un intuitive and a
> user hassle. We should get rid of it and allow users to say that the created
> archive should be relative to some absolute path and throw an excpetion if
> the input does not confirm to the relative absolute path.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
