[
https://issues.apache.org/jira/browse/HADOOP-19951?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18106547#comment-18106547
]
ASF GitHub Bot commented on HADOOP-19951:
-----------------------------------------
hadoop-yetus commented on PR #8654:
URL: https://github.com/apache/hadoop/pull/8654#issuecomment-5367804383
:broken_heart: **-1 overall**
| Vote | Subsystem | Runtime | Logfile | Comment |
|:----:|----------:|--------:|:--------:|:-------:|
| +0 :ok: | reexec | 0m 0s | | Docker mode activated. |
| -1 :x: | patch | 0m 23s | |
https://github.com/apache/hadoop/pull/8654 does not apply to trunk. Rebase
required? Wrong Branch? See
https://cwiki.apache.org/confluence/display/HADOOP/How+To+Contribute for help.
|
| Subsystem | Report/Notes |
|----------:|:-------------|
| GITHUB PR | https://github.com/apache/hadoop/pull/8654 |
| Console output |
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-8654/28/console |
| versions | git=2.34.1 |
| Powered by | Apache Yetus 0.14.1 https://yetus.apache.org |
This message was automatically generated.
> 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
> Assignee: PJ Fanning
> Priority: Major
> Labels: pull-request-available
> Fix For: 3.6.0
>
>
> 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]
