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

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

                Author: ASF GitHub Bot
            Created on: 12/Oct/21 15:59
            Start Date: 12/Oct/21 15:59
    Worklog Time Spent: 10m 
      Work Description: aajisaka commented on pull request #3529:
URL: https://github.com/apache/hadoop/pull/3529#issuecomment-941148410


   Thank you @virajjasani for your patch. There are 3 remaining usages under 
hadoop-tools:
   - TestHadoopArchiveLogs.java
   - TestS3AInputStreamRetry.java
   - ITestS3SelectCLI.java
   
   Would you fix them?


-- 
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.

To unsubscribe, e-mail: [email protected]

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


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

    Worklog Id:     (was: 664145)
    Time Spent: 1h 50m  (was: 1h 40m)

> Replace all default Charset usage with UTF-8
> --------------------------------------------
>
>                 Key: HADOOP-17956
>                 URL: https://issues.apache.org/jira/browse/HADOOP-17956
>             Project: Hadoop Common
>          Issue Type: Task
>            Reporter: Viraj Jasani
>            Assignee: Viraj Jasani
>            Priority: Major
>              Labels: pull-request-available
>          Time Spent: 1h 50m
>  Remaining Estimate: 0h
>
> As discussed on PR#3515, creating this sub-task to replace all default 
> charset with UTF-8 as default charset has some potential problems (e.g. 
> HADOOP-11379, HADOOP-11389).
> FYI [~aajisaka]



--
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