[
https://issues.apache.org/jira/browse/HADOOP-3663?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12632040#action_12632040
]
Mahadev konar commented on HADOOP-3663:
---------------------------------------
hmm... :) the code in the mapper just filters any paths that should not be
part of the archive. It just calls a function and there are 3 line changes for
that. Neway if its cofusing for someone there must be somethign wrong with the
code :). I dont have the bandwidth to fix this (as mentioned above) by the code
freeze date. Ill leave it as it is. If people think that this needs to go into
0.19 I think this patch should be good...
> 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.
