[
https://issues.apache.org/jira/browse/HADOOP-19231?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17874682#comment-17874682
]
ASF GitHub Bot commented on HADOOP-19231:
-----------------------------------------
ayushtkn commented on PR #6953:
URL: https://github.com/apache/hadoop/pull/6953#issuecomment-2295310885
The HBase stuff is bit tricky, for the HBase test we use the older Hadoop
version, which is compatible with the HBase release we are using. It is
hardcoded here:
https://github.com/apache/hadoop/blob/b5f88990b721aebe84d4bbf97ed2fdfbd0f42854/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/pom.xml#L32
I think this problem is bit similar to
[YARN-8856](https://issues.apache.org/jira/browse/YARN-8856)
> add JacksonUtil to centralise some code
> ---------------------------------------
>
> Key: HADOOP-19231
> URL: https://issues.apache.org/jira/browse/HADOOP-19231
> Project: Hadoop Common
> Issue Type: Task
> Affects Versions: 3.4.0, 3.4.1
> Reporter: PJ Fanning
> Priority: Major
> Labels: pull-request-available
> Fix For: 3.5.0
>
>
> To future proof Hadoop against Jackson changes, it makes sense to not just
> create ObjectMappers and JsonFactories in many different places in the Hadoop
> code.
> One of the main drivers of this is
> https://www.javadoc.io/doc/com.fasterxml.jackson.core/jackson-core/latest/com/fasterxml/jackson/core/StreamReadConstraints.html
>
> Jackson 3 (not yet scheduled for release) has some fairly big API and
> behaviour changes too.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
