[
https://issues.apache.org/jira/browse/HADOOP-12705?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15644932#comment-15644932
]
Sean Mackrory commented on HADOOP-12705:
----------------------------------------
Just attached one - didn't see any required changes other than the POM.
One lingering concern I have is that while I understand the need for more
coordination in branch-2, the minor changes required if we did move to 2.8.x in
3.0 seem smaller to me than the danger in being locked into 2.7.x for the life
of Hadoop 3, where incompatible changes soon become even worse. Granted,
there's also no guarantee that 2.9.x won't *also* contain incompatible changes,
so I could just be fighting a losing battle, but wanted to raise the concern.
> Upgrade Jackson 2.2.3 to 2.7.x or later
> ---------------------------------------
>
> Key: HADOOP-12705
> URL: https://issues.apache.org/jira/browse/HADOOP-12705
> Project: Hadoop Common
> Issue Type: Sub-task
> Components: build
> Affects Versions: 2.8.0
> Reporter: Steve Loughran
> Attachments: HADOOP-12705.002.patch, HADOOP-12705.003.patch,
> HADOOP-12705.01.patch, HADOOP-13050-001.patch
>
>
> There's no rush to do this; this is just the JIRA to track versions. However,
> without the upgrade, things written for Jackson 2.4.4 can break ( SPARK-12807)
> being Jackson, this is a potentially dangerous update.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
