You are viewing a plain text version of this content. The canonical link for it is here.
Posted to common-issues@hadoop.apache.org by "Allen Wittenauer (JIRA)" <ji...@apache.org> on 2011/04/16 01:20:05 UTC

[jira] [Created] (HADOOP-7228) jar names are not compatible with 0.20.2

jar names are not compatible with 0.20.2
----------------------------------------

                 Key: HADOOP-7228
                 URL: https://issues.apache.org/jira/browse/HADOOP-7228
             Project: Hadoop Common
          Issue Type: Bug
          Components: documentation
    Affects Versions: 0.20.203.0
            Reporter: Allen Wittenauer
            Priority: Critical


The jars in 203 are named differently vs. Apache Hadoop 0.20.2.  I understand this was done to make the Maven people less cranky.  However, this breaks compatibility especially for streaming users. We need to make sure we have a release note or something significant so that users aren't taken by surprise.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (HADOOP-7228) jar names are not compatible with 0.20.2

Posted by "Allen Wittenauer (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/HADOOP-7228?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13112895#comment-13112895 ] 

Allen Wittenauer commented on HADOOP-7228:
------------------------------------------

Pretty much too late.   branch-20-security is all about breaking compatibility with 0.20.[0-2] it seems.

> jar names are not compatible with 0.20.2
> ----------------------------------------
>
>                 Key: HADOOP-7228
>                 URL: https://issues.apache.org/jira/browse/HADOOP-7228
>             Project: Hadoop Common
>          Issue Type: Bug
>          Components: documentation
>    Affects Versions: 0.20.203.0
>            Reporter: Allen Wittenauer
>            Priority: Critical
>
> The jars in 203 are named differently vs. Apache Hadoop 0.20.2.  I understand this was done to make the Maven people less cranky.  However, this breaks compatibility especially for streaming users. We need to make sure we have a release note or something significant so that users aren't taken by surprise.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[jira] [Resolved] (HADOOP-7228) jar names are not compatible with 0.20.2

Posted by "Allen Wittenauer (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/HADOOP-7228?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Allen Wittenauer resolved HADOOP-7228.
--------------------------------------

    Resolution: Won't Fix

Surprise.

> jar names are not compatible with 0.20.2
> ----------------------------------------
>
>                 Key: HADOOP-7228
>                 URL: https://issues.apache.org/jira/browse/HADOOP-7228
>             Project: Hadoop Common
>          Issue Type: Bug
>          Components: documentation
>    Affects Versions: 0.20.203.0
>            Reporter: Allen Wittenauer
>            Priority: Critical
>
> The jars in 203 are named differently vs. Apache Hadoop 0.20.2.  I understand this was done to make the Maven people less cranky.  However, this breaks compatibility especially for streaming users. We need to make sure we have a release note or something significant so that users aren't taken by surprise.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[jira] [Commented] (HADOOP-7228) jar names are not compatible with 0.20.2

Posted by "Eli Collins (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/HADOOP-7228?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13112280#comment-13112280 ] 

Eli Collins commented on HADOOP-7228:
-------------------------------------

I patched CDH to preserve the old jar names via symlinks since breaking compatibility wasn't an option. Can cherry pick it into branch-20-security if you like the fix.

commit 9b72d268a0b590b4fd7d13aca17c1c453f8bc957
Author: Eli Collins <el...@cloudera.com>
Date:   Sun Jun 27 18:42:45 2010 -0700

    CLOUDERA-BUILD. Make symlinks so old hadoop jar names are preserved (CDH-1543).

> jar names are not compatible with 0.20.2
> ----------------------------------------
>
>                 Key: HADOOP-7228
>                 URL: https://issues.apache.org/jira/browse/HADOOP-7228
>             Project: Hadoop Common
>          Issue Type: Bug
>          Components: documentation
>    Affects Versions: 0.20.203.0
>            Reporter: Allen Wittenauer
>            Priority: Critical
>
> The jars in 203 are named differently vs. Apache Hadoop 0.20.2.  I understand this was done to make the Maven people less cranky.  However, this breaks compatibility especially for streaming users. We need to make sure we have a release note or something significant so that users aren't taken by surprise.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira