[
https://issues.apache.org/jira/browse/RANGER-4327?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17805901#comment-17805901
]
Bhavik Patel commented on RANGER-4327:
--------------------------------------
This issue is observed as jackson-1.x version is removed in the hadoop-3.4 :
[https://github.com/apache/hadoop/commit/04b6b9a87bf024e82aa50328b4994aea4268d98e#diff-635a9ebcc70f58d8ca1c55b0d78cc90064a5081d189162a432271778da3cf018]
>From ranger end also we have to remove jackson-1.x version as it's vulnerable.
> Make ranger2.4 hdfs plugin compatible with hadoop 3.3.5 +
> ---------------------------------------------------------
>
> Key: RANGER-4327
> URL: https://issues.apache.org/jira/browse/RANGER-4327
> Project: Ranger
> Issue Type: Improvement
> Components: plugins
> Affects Versions: 2.3.0, 2.4.0
> Reporter: caijialiang
> Assignee: caijialiang
> Priority: Major
> Attachments: image-2023-07-25-17-30-18-136.png,
> image-2023-07-26-13-40-10-555.png, patch3-RANGER-4327.diff
>
>
> hadoop 3.3.5 has upgraded its jackson dependency and removed all jackson 1.x
> packages, including the jackson-jaxrs jar. As a result, when starting with
> the Ranger plugin enabled, Hadoop namenode fails to start due to the
> inability to load jackson 1.x.
> To address this issue and ensure compatibility with the Hadoop 3.3.5 upgrade,
> we need to package jackson 1.x jars in the hdfs plugin as well,like the Ozone
> did https://issues.apache.org/jira/browse/RANGER-2818. This will allow the
> namenode to start successfully.
> !image-2023-07-26-13-40-10-555.png!
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
