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 "Laszlo Gaal (Jira)" <ji...@apache.org> on 2025/09/04 19:27:00 UTC
[jira] [Resolved] (IMPALA-13025) Use AWSCLI v2 for bucket uploads during toolchain builds
[ https://issues.apache.org/jira/browse/IMPALA-13025?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Laszlo Gaal resolved IMPALA-13025.
----------------------------------
Fix Version/s: Impala 5.0.0
Resolution: Fixed
https://github.com/cloudera/native-toolchain/commit/b5e46bcd183111f66e54c65c5ce7288f59586488
IMPALA-13025: Upgrade AWSCLI to v2 in toolchain build containers
IMPALA-12697 exposed AWSCLIv1 as a potential cause for build breaks:
occasionally it throws segfaults during S3 bucket uploads when executed
on an ARM-based instance.
This patch replaces AWSCLIv1 with AWSCLIv2 in the toolchain build
container images hoping to avoid this failure.
Add architecture-dependent env var to signature download
Change-Id: Id4d451bd69cc68f1bc0ec5f73527a3a9f1a59219
Reviewed-on: http://gerrit.cloudera.org:8080/23129
Reviewed-by: Michael Smith <mi...@cloudera.com>
Tested-by: Laszlo Gaal <la...@cloudera.com>
> Use AWSCLI v2 for bucket uploads during toolchain builds
> --------------------------------------------------------
>
> Key: IMPALA-13025
> URL: https://issues.apache.org/jira/browse/IMPALA-13025
> Project: IMPALA
> Issue Type: Improvement
> Components: Toolchain
> Affects Versions: Impala 3.4.0, Impala 4.3.0
> Reporter: Laszlo Gaal
> Assignee: Laszlo Gaal
> Priority: Major
> Fix For: Impala 5.0.0
>
>
> IMPALA-12697 exposed an unexpected failure mode during toolchain builds: AWSCLI may segfault when running S3 uploads on ARM-based instances, patched over by a band-aid of failing the build when such an upload failure was detected.
> This ticket intends to work around the root cause of that failure by upgrading AWSCLI in the toolchain build containers to AWSCLI v2, hoping that it is in a better maintained shape.
> replacing AWSCLI v1 (which is based on the system's installed Python version) with v2 (which encapsulates its own Python runtime) is acceptable because there are no implicit dependencies on AWSCLI components (e.g. boto3 or botocore) in the toolchain build.
--
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