[
https://issues.apache.org/jira/browse/MAPREDUCE-739?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12732291#action_12732291
]
Chris Douglas commented on MAPREDUCE-739:
-----------------------------------------
{noformat}
[exec] +1 overall.
[exec]
[exec] +1 @author. The patch does not contain any @author tags.
[exec]
[exec] +1 tests included. The patch appears to include 34 new or
modified tests.
[exec]
[exec] +1 javadoc. The javadoc tool did not generate any warning
messages.
[exec]
[exec] +1 javac. The applied patch does not increase the total number
of javac compiler warnings.
[exec]
[exec] +1 findbugs. The patch does not introduce any new Findbugs
warnings.
[exec]
[exec] +1 release audit. The applied patch does not increase the
total number of release audit warnings.
{noformat}
The new patch makes no functional changes, so the test result for the last run
(unrelated streaming test failures) is sufficient
> 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, MAPREDUCE-739.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.
