crunch-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Tom White (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (CRUNCH-235) Avoid exposing incompatible Hadoop classes in Crunch API
Date Tue, 09 Jul 2013 16:17:50 GMT

     [ https://issues.apache.org/jira/browse/CRUNCH-235?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Tom White resolved CRUNCH-235.
------------------------------

       Resolution: Fixed
    Fix Version/s: 0.7.0

I just committed this. Thanks for the review Josh.
                
> Avoid exposing incompatible Hadoop classes in Crunch API
> --------------------------------------------------------
>
>                 Key: CRUNCH-235
>                 URL: https://issues.apache.org/jira/browse/CRUNCH-235
>             Project: Crunch
>          Issue Type: Improvement
>          Components: Core
>            Reporter: Tom White
>            Assignee: Tom White
>             Fix For: 0.7.0
>
>         Attachments: CRUNCH-235.patch
>
>
> Between Hadoop 1 and 2, org.apache.hadoop.mapreduce.Counter changed from a class to an
interface. Therefore, exposing Counter in Crunch's API means that Crunch programs may need
to be recompiled when moving from a Hadoop 1 to a Hadoop 2 cluster. It would be nice to avoid
the need to recompile. 
> Note that Crunch itself has two artifacts - one for each major version of Hadoop - and
the change proposed here would not alter that, it would just mean that the same Crunch program
binary could be used with either Crunch artifact.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message