hadoop-mapreduce-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Peter Bacsko (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (MAPREDUCE-6937) Backport MAPREDUCE-6870 to branch-2 while preserving compatibility
Date Tue, 29 Aug 2017 10:24:01 GMT

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

Peter Bacsko commented on MAPREDUCE-6937:

Wow, this build looks bad. I've taken a look at the various problems:

* White space issues - these was not introduced by the patch
* Failing unit tests - could not reproduce those (all of them are related to some sort of
* Findbugs - not introduced by this patch
* ASF license - totally unrelated (looks like it checked some temporarily created files)
* Checkstyle - seems legit, I'll address them

> Backport MAPREDUCE-6870 to branch-2 while preserving compatibility
> ------------------------------------------------------------------
>                 Key: MAPREDUCE-6937
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-6937
>             Project: Hadoop Map/Reduce
>          Issue Type: Improvement
>            Reporter: Zhe Zhang
>            Assignee: Erik Krogen
>         Attachments: MAPREDUCE-6870-branch-2.01.patch, MAPREDUCE-6870-branch-2.7.03.patch,
MAPREDUCE-6870_branch2.7.patch, MAPREDUCE-6870_branch2.7v2.patch, MAPREDUCE-6870-branch-2.8.03.patch,
MAPREDUCE-6870_branch2.8.patch, MAPREDUCE-6870_branch2.8v2.patch
> To maintain compatibility we need to disable this by default per discussion on MAPREDUCE-6870.
> Using a separate JIRA to correctly track incompatibilities.

This message was sent by Atlassian JIRA

To unsubscribe, e-mail: mapreduce-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: mapreduce-issues-help@hadoop.apache.org

View raw message