[
https://issues.apache.org/jira/browse/HADOOP-10026?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13787744#comment-13787744
]
Steve Loughran commented on HADOOP-10026:
-----------------------------------------
# the jenkins complaint is because the patch has to start at trunk -can you
recreate it from there?
# Why upgrade? What benefits does it bring? What is the price of not upgrading?
# what is the minimum version of jackson needed for the new API
hadoop-openstack isn't shipping yet, so changes there may not be as dangerous.
It uses JSON in two places: auth and directory listings. For Auth we don't care
about performance, though we do care about authenticating with different
openstack implementations, so the new API would need to be tested against:
rackspace US, UK, and HP cloud, leaving rackspace & other openstack developers
(such as Mirantis) to test against the pre-release stuff. It proved
surprisingly brittle and I'd be very reluctant to change it unless it was
particularly compelling.
> Upgrade to Jackson 2
> --------------------
>
> Key: HADOOP-10026
> URL: https://issues.apache.org/jira/browse/HADOOP-10026
> Project: Hadoop Common
> Issue Type: Task
> Reporter: Ben McCann
> Attachments: hadoop-tools-openstack-jackson.patch
>
>
> I'd like to see Hadoop upgrade to Jackson 2. This is a change that should be
> able to be made to each Hadoop project one at a time, so I've attached a
> patch for the first and will follow up with others if this one is committed.
--
This message was sent by Atlassian JIRA
(v6.1#6144)
