[
https://issues.apache.org/jira/browse/MAPREDUCE-739?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mahadev konar updated MAPREDUCE-739:
------------------------------------
Attachment: MAPREDUCE-739.patch
this patch adds an argument
{code}
archiveName <> -p paretnPath <src>* <dest>
{code}
here all the files will be archived relative to parentPath. If the user has
only one directory and wants the archived files relative to that then
{code}
archiveName <> -p paretnPath <dest> can be used.
{code}
- the new argument is mandatory and is required. This is a change from old
versions but given that this will make usability much easier it will makes
things easy to understand.
- the old archives is still readalbe from this new code (the old archives that
were created pre 0.21 will be readable still)
- also incorpiorated hairong's comments to make the code much easier to read.
- update forrest docs with better examples in common jira HADOOP-6142.
> Allow relative paths to be created inside archives.
> ---------------------------------------------------
>
> Key: MAPREDUCE-739
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-739
> Project: Hadoop Map/Reduce
> Issue Type: Improvement
> Components: harchive
> Reporter: Mahadev konar
> Assignee: Mahadev konar
> Fix For: 0.21.0
>
> Attachments: HADOOP-3663.patch, HADOOP-3663.patch, HADOOP-3663.patch,
> MAPREDUCE-739.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.
