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

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

                Author: ASF GitHub Bot
            Created on: 30/Jun/22 12:30
            Start Date: 30/Jun/22 12:30
    Worklog Time Spent: 10m 
      Work Description: ahmarsuhail commented on code in PR #4520:
URL: https://github.com/apache/hadoop/pull/4520#discussion_r910969010


##########
hadoop-tools/hadoop-aws/src/main/java/org/apache/hadoop/fs/s3a/S3AFileSystem.java:
##########
@@ -1573,7 +1560,7 @@ protected S3AReadOpContext createReadContext(
         statistics,
         statisticsContext,
         fileStatus,
-        futurePool,
+        unboundedThreadPool,

Review Comment:
   that's my bad, it should be `boundedThreadPool`. Have updated





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

    Worklog Id:     (was: 786549)
    Time Spent: 8h 10m  (was: 8h)

> Remove use of scala jar twitter util-core with java futures in S3A 
> prefetching stream
> -------------------------------------------------------------------------------------
>
>                 Key: HADOOP-18180
>                 URL: https://issues.apache.org/jira/browse/HADOOP-18180
>             Project: Hadoop Common
>          Issue Type: Sub-task
>          Components: fs/s3
>    Affects Versions: 3.4.0
>            Reporter: PJ Fanning
>            Assignee: PJ Fanning
>            Priority: Major
>              Labels: pull-request-available
>             Fix For: 3.4.0
>
>          Time Spent: 8h 10m
>  Remaining Estimate: 0h
>
> This jar will cause trouble for scala projects like spark that use different 
> scala versions from the scala 2.11 used in the twitter util-core



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

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

Reply via email to