[HADOOP-18176] s3a prefetching stream to move off twitter FuturePool

• Type: Sub-task
• Status: Resolved
• Priority: Major
• Resolution: Duplicate
• Affects Version/s: 3.4.0
• Component/s: fs/s3
• Assignee: Unassigned
• Reporter: Steve Loughran
• Created: 25/Mar/22 20:36
• Updated: 28/Mar/22 14:32
• Resolved: 28/Mar/22 14:32

Description

This has to be a blocker for the merge I'm afraid: move off twitter's util lib and its future pool

it's not just another jar, its a full scala runtime. and as we know, that's a very brittle runtime. for existing scala code. that's their problem...we don't want to get involved in this

[INFO] +- com.twitter:util-core_2.11:jar:21.2.0:compile
[INFO] |  +- org.scala-lang:scala-library:jar:2.11.12:compile
[INFO] |  +- com.twitter:util-function_2.11:jar:21.2.0:compile
[INFO] |  +- org.scala-lang.modules:scala-collection-compat_2.11:jar:2.1.2:compile
[INFO] |  +- org.scala-lang:scala-reflect:jar:2.11.12:compile
[INFO] |  \- org.scala-lang.modules:scala-parser-combinators_2.11:jar:1.1.2:compile

Issue Links

• duplicates: HADOOP-18180 Remove use of scala jar twitter util-core with java futures in S3A prefetching stream