[ 
https://issues.apache.org/jira/browse/IMPALA-12502?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17803391#comment-17803391
 ] 

ASF subversion and git services commented on IMPALA-12502:
----------------------------------------------------------

Commit 52bb27b1b57f48594ef47cbf99223523ca16ce06 in impala's branch 
refs/heads/master from wzhou-code
[ https://gitbox.apache.org/repos/asf?p=impala.git;h=52bb27b1b ]

IMPALA-12671: Fix LdapHS2Test.testImpalaExtJdbcTables for JDK17 build

LdapHS2Test.testImpalaExtJdbcTables was added in IMPALA-12502 recently.
The test failed in nightly builds with JDK17. The error happened when
shell script testdata/bin/download-impala-jdbc-driver.sh was invoked
from Java code to copy Impala jdbc driver with hadoop fs commands.

This patch changes code to run the script download-impala-jdbc-driver.sh
from testdata/bin/copy-ext-data-sources.sh, which is invoked when
loading data and jar files for external data source.

Testing:
 - Passed LdapHS2Test.testImpalaExtJdbcTables for JDK17 and default
   build JDK.
 - Passed core tests.

Change-Id: If62fe207978301b8ce95f5af30f605e3bb8caa28
Reviewed-on: http://gerrit.cloudera.org:8080/20851
Reviewed-by: Impala Public Jenkins <[email protected]>
Tested-by: Impala Public Jenkins <[email protected]>


> Support Impala to Impala federation
> -----------------------------------
>
>                 Key: IMPALA-12502
>                 URL: https://issues.apache.org/jira/browse/IMPALA-12502
>             Project: IMPALA
>          Issue Type: Sub-task
>          Components: Backend, Frontend
>            Reporter: Wenzhe Zhou
>            Assignee: Wenzhe Zhou
>            Priority: Major
>             Fix For: Impala 4.4.0
>
>
> Support to read Impala tables from another Impala cluster through JDBC 
> external data source



--
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