[
https://issues.apache.org/jira/browse/HADOOP-16485?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16912860#comment-16912860
]
Duo Zhang commented on HADOOP-16485:
------------------------------------
OK, sometimes in the past we upgraded the jackson dependencies from 1.x to 2.x,
and I believe this also breaks the compatibility. So what is the rule? We can
only do this for major release or even minor release?
> Remove dependency on jackson
> ----------------------------
>
> Key: HADOOP-16485
> URL: https://issues.apache.org/jira/browse/HADOOP-16485
> Project: Hadoop Common
> Issue Type: Improvement
> Reporter: Wei-Chiu Chuang
> Priority: Major
>
> Looking at git history, there were 5 commits related to updating jackson
> versions due to various CVEs since 2018. And it seems to get worse more
> recently.
> File this jira to discuss the possibility of removing jackson dependency once
> for all. I see that jackson is deeply integrated into Hadoop codebase, so not
> a trivial task. However, if Hadoop is forced to make a new set of releases
> because of Jackson vulnerabilities, it may start to look not so costly.
> At the very least, consider stripping jackson-databind coode, since that's
> where the majority of CVEs come from.
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
