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

Posted to commits@impala.apache.org by ta...@apache.org on 2019/01/18 00:46:59 UTC

[impala] 01/04: IMPALA-8061: Fix S3_ACCESS_VALIDATED unbound variable

This is an automated email from the ASF dual-hosted git repository.

tarmstrong pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/impala.git

commit e6b492ad11a94a5d9a36e1d101481cc7c3d33acf
Author: Fredy Wijaya <fw...@cloudera.com>
AuthorDate: Tue Jan 8 19:26:06 2019 -0800

    IMPALA-8061: Fix S3_ACCESS_VALIDATED unbound variable
    
    This patch fixes S3_ACCESS_VALIDATED unbound variable by initializing
    the S3_ACCESS_VALIDATED to 0 when TARGET_FILESYSTEM=s3.
    
    Testing:
    - Ran S3_BUCKET=impala-test TARGET_FILESYSTEM=s3 ./buildall.sh
    
    Change-Id: If48866bb71d748f12ceada4fd62822d7d374811c
    Reviewed-on: http://gerrit.cloudera.org:8080/12193
    Reviewed-by: Impala Public Jenkins <im...@cloudera.com>
    Tested-by: Impala Public Jenkins <im...@cloudera.com>
---
 bin/impala-config.sh | 1 +
 1 file changed, 1 insertion(+)

diff --git a/bin/impala-config.sh b/bin/impala-config.sh
index 230554f..399d953 100755
--- a/bin/impala-config.sh
+++ b/bin/impala-config.sh
@@ -330,6 +330,7 @@ fi
 if [ "${TARGET_FILESYSTEM}" = "s3" ]; then
   # We guard the S3 access check with a variable. This check hits a rate-limited endpoint
   # on AWS and multiple inclusions of S3 can exceed the limit, causing the check to fail.
+  S3_ACCESS_VALIDATED="${S3_ACCESS_VALIDATED-0}"
   if [[ "${S3_ACCESS_VALIDATED}" -ne 1 ]]; then
     if ${IMPALA_HOME}/bin/check-s3-access.sh; then
       export S3_ACCESS_VALIDATED=1