[
https://issues.apache.org/jira/browse/HADOOP-6945?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12907292#action_12907292
]
Scott Carey commented on HADOOP-6945:
-------------------------------------
+1. And this is a big enough annoyance to back-port to 0.20. It clearly has
very small scope of breaking things (HADOOP-6184). I currently remove the
jackson jar from the hadoop lib dir on all my nodes (CDH3 0.20).
As long as so many hadoop jars come first in a task's path, any feature that
creates a new jar dependency should be _heavily_ scrutinized before inclusion.
> Inclusion of Old Jackson-JSON Breaks tasks using Avro (or any task depending
> on Jackson JSON)
> ---------------------------------------------------------------------------------------------
>
> Key: HADOOP-6945
> URL: https://issues.apache.org/jira/browse/HADOOP-6945
> Project: Hadoop Common
> Issue Type: Bug
> Affects Versions: 0.21.0
> Reporter: Greg Wittel
>
> HADOOP-6184 added the ability to serialize the Configuration to JSON.
> However its inclusion of jackson-1.0.1 means that any map-reduce task that
> depends (directly or indirectly) on Jackson, can only use Jackson 1.0.1 APIs.
> The 100% fix is to give the task's classpath priority over the core/common
> classpath (MAPREDUCE-1700/MAPREDUCE-1938) so that a job can use newer
> revisions of the library.
> For a nearer term fix, is it possible to upgrade the included Jackson library
> to a recent version (1.5.x+)? The APIs are backwards compatible.
> alernatively, its possible to eliminate the use of Jackson for this minor
> feature as the Configuration object could be serialized to JSON without a 3rd
> party library.
> An ancilliary issue is that the jackson.version referenced in ivy.xml is
> never specified in the source tree (ivy/libraries.properties).
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
