[
https://issues.apache.org/jira/browse/HADOOP-6945?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13028755#comment-13028755
]
Steve Loughran commented on HADOOP-6945:
----------------------------------------
given that Jackson is only used to serialize the config, and also that
generating valid JSON is fairly straightforward, why not get rid of the jackson
dependency at all and just have a json serializer class? jackson (or something
like json-lib or gson) could just be used to validate the content in the unit
tests.
> 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.
For more information on JIRA, see: http://www.atlassian.com/software/jira
