You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues-all@impala.apache.org by "Michael Smith (Jira)" <ji...@apache.org> on 2022/11/14 21:26:00 UTC

[jira] [Resolved] (IMPALA-11524) Remove workaround when HADOOP-18410 is fixed

     [ https://issues.apache.org/jira/browse/IMPALA-11524?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Michael Smith resolved IMPALA-11524.
------------------------------------
    Fix Version/s: Impala 4.2.0
       Resolution: Fixed

> Remove workaround when HADOOP-18410 is fixed
> --------------------------------------------
>
>                 Key: IMPALA-11524
>                 URL: https://issues.apache.org/jira/browse/IMPALA-11524
>             Project: IMPALA
>          Issue Type: Task
>          Components: Infrastructure
>    Affects Versions: Impala 4.2.0
>            Reporter: Joe McDonnell
>            Priority: Major
>             Fix For: Impala 4.2.0
>
>
> IMPALA-11514 worked around HADOOP-18410 by specifying fs.s3a.input.async.drain.threshold=512G in core-site.xml. Once HADOOP-18410 is fixed and Impala is building against that fixed version, we should remove this workaround.



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

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-all-unsubscribe@impala.apache.org
For additional commands, e-mail: issues-all-help@impala.apache.org