[ 
https://issues.apache.org/jira/browse/MAPREDUCE-739?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12732223#action_12732223
 ] 

Todd Lipcon commented on MAPREDUCE-739:
---------------------------------------

bq. -1 release audit. The applied patch generated 317 release audit warnings 
(more than the trunk's current 315 warnings).

The release audit diff is:
{quote}
121d120
<      [java]  !????? 
/home/hudson/hudson-slave/workspace/Mapreduce-Patch-vesta.apache.org/trunk/build/hadoop-mapred-794101_MAPREDUCE-739_PATCH-12413485/docs/jdiff/changes/org.apache.hadoop.tools.HadoopArchives.html
129d127
<      [java]  !????? 
/home/hudson/hudson-slave/workspace/Mapreduce-Patch-vesta.apache.org/trunk/build/hadoop-mapred-794101_MAPREDUCE-739_PATCH-12413485/docs/jdiff/changes/pkg_org.apache.hadoop.tools.html
{quote}

This patch doesn't touch those packages, so I think we can ignore this:
{noformat}
 .../org/apache/hadoop/fs/ChecksumFileSystem.java   |    5 +-
 src/java/org/apache/hadoop/util/DataChecksum.java  |   10 +-
 src/java/org/apache/hadoop/util/PureJavaCrc32.java |  351 ++++++++++++++++++++
 .../org/apache/hadoop/util/TestPureJavaCrc32.java  |  171 ++++++++++
{noformat}

bq. -1 contrib tests. The patch failed contrib unit tests.

Only failed Streaming tests which are failing on trunk.

> 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
>
>
> 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.

Reply via email to