[ 
https://issues.apache.org/jira/browse/HADOOP-17371?focusedWorklogId=529620&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-529620
 ]

ASF GitHub Bot logged work on HADOOP-17371:
-------------------------------------------

                Author: ASF GitHub Bot
            Created on: 30/Dec/20 20:32
            Start Date: 30/Dec/20 20:32
    Worklog Time Spent: 10m 
      Work Description: jojochuang commented on pull request #2453:
URL: https://github.com/apache/hadoop/pull/2453#issuecomment-752749363


   @Sushmasree-28 thanks for the review. I updated the PR to address these two 
tetsts. However, please note that we use sendError() throughout the codebase. 
Unless they break tests I suggest we postpone any further changes to a future 
jira.


----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
[email protected]


Issue Time Tracking
-------------------

    Worklog Id:     (was: 529620)
    Time Spent: 2h 40m  (was: 2.5h)

> Bump Jetty to the latest version 9.4.34
> ---------------------------------------
>
>                 Key: HADOOP-17371
>                 URL: https://issues.apache.org/jira/browse/HADOOP-17371
>             Project: Hadoop Common
>          Issue Type: Improvement
>    Affects Versions: 3.3.1, 3.4.0, 3.1.5, 3.2.3
>            Reporter: Wei-Chiu Chuang
>            Assignee: Wei-Chiu Chuang
>            Priority: Major
>              Labels: pull-request-available
>          Time Spent: 2h 40m
>  Remaining Estimate: 0h
>
> The Hadoop 3 branches are on 9.4.20. We should update to the latest version: 
> 9.4.34



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to