You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@crunch.apache.org by "Tom White (JIRA)" <ji...@apache.org> on 2013/07/05 12:35:48 UTC
[jira] [Updated] (CRUNCH-235) Avoid exposing incompatible Hadoop
classes in Crunch API
[ https://issues.apache.org/jira/browse/CRUNCH-235?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Tom White updated CRUNCH-235:
-----------------------------
Attachment: CRUNCH-235.patch
This patch deprecates and provides alternatives for public methods that expose Counter.
> 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
> 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