[
https://issues.apache.org/jira/browse/HADOOP-19951?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18105954#comment-18105954
]
ASF GitHub Bot commented on HADOOP-19951:
-----------------------------------------
pan3793 commented on PR #8654:
URL: https://github.com/apache/hadoop/pull/8654#issuecomment-5344003478
Another finding: Same-class issue still open: `getMountTable()`
(`RBFMetrics.java:295`) still puts a raw `List<RemoteLocation>` under
`destinations` (`getJson` at `RBFMetrics.java:1005`; `RemoteLocation` is not a
`BaseRecord`). Verified with Jetty 9.4 vs Jackson 2.18.9:
`"destinations":["ns0->/dest"]` becomes
`"destinations":[{"dest":"/dest","nameserviceId":"ns0","rpcAddress":"ns0->/dest"}]`.
JMX-visible via `FederationMBean.getMountTable()`, and no test asserts it.
> Drop use of jetty-util-ajax and use jackson instead
> ---------------------------------------------------
>
> Key: HADOOP-19951
> URL: https://issues.apache.org/jira/browse/HADOOP-19951
> Project: Hadoop Common
> Issue Type: Task
> Reporter: PJ Fanning
> Priority: Major
> Labels: pull-request-available
>
> Hadoop uses jetty-util-ajax in a few modules to read and write JSON.
> This is a part of HADOOP-19912 that can be split out and it doesn't cause the
> same issues with worrying about jar compatibilities - it actually simplifies
> the build by removing a direct dependency.
> The aim here is to reduce the number of ways that Hadoop works with JSON and
> Jackson is more commonly used in Hadoop than jetty-util-ajax.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
