[
https://issues.apache.org/jira/browse/IMPALA-15383?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18117250#comment-18117250
]
Quanlong Huang commented on IMPALA-15383:
-----------------------------------------
The failure is
{noformat}
2026-09-19 06:16:56
URL:https://downloads.cloudera.com/connectors/ClouderaImpalaJDBC-2.6.39.1073.zip
[38557021/38557021] -> "ClouderaImpalaJDBC-2.6.39.1073.zip" [1]
Traceback (most recent call last):
File "./unzip.py", line 3, in <module>
pzf = PyZipFile(sys.argv[1])
File "/usr/lib/python3.8/zipfile.py", line 1973, in __init__
ZipFile.__init__(self, file, mode=mode, compression=compression,
File "/usr/lib/python3.8/zipfile.py", line 1253, in __init__
self.fp = io.open(file, filemode)
FileNotFoundError: [Errno 2] No such file or directory:
'ClouderaImpalaJDBC-2.6.39.1073/ClouderaImpalaJDBC42-2.6.39.1073.zip'{noformat}
The code is
{code:bash}
58 # Extract driver jar file from zip file.
59 python3 ./unzip.py ${SIMBA_DRIVER_ZIP_FILENAME}.zip
60 python3 ./unzip.py
${SIMBA_DRIVER_ZIP_FILENAME}/${INNER_SIMBA_DRIVER_ZIP_FILENAME}.zip{code}
The test code expects that after extracting ClouderaImpalaJDBC-2.6.39.1073.zip,
there is an inner zip file
ClouderaImpalaJDBC-2.6.39.1073/ClouderaImpalaJDBC42-2.6.39.1073.zip to extract,
which produces the jar file.
But now the layout of ClouderaImpalaJDBC-2.6.39.1073.zip is
{noformat}
ClouderaImpalaJDBC-2.6.39.1073/
ClouderaImpalaJDBC-2.6.39.1073/Software Quality Report for Impala JDBC
2.6.39.1073.pdf
ClouderaImpalaJDBC-2.6.39.1073/ClouderaImpalaJDBC42-2.6.39.1073/
ClouderaImpalaJDBC-2.6.39.1073/ClouderaImpalaJDBC42-2.6.39.1073/libs/
ClouderaImpalaJDBC-2.6.39.1073/ClouderaImpalaJDBC42-2.6.39.1073/libs/LeanImpalaJDBC42.jar
ClouderaImpalaJDBC-2.6.39.1073/ClouderaImpalaJDBC42-2.6.39.1073/ImpalaJDBC42.jar
ClouderaImpalaJDBC-2.6.39.1073/ClouderaImpalaJDBC42-2.6.39.1073/EULA.txt
ClouderaImpalaJDBC-2.6.39.1073/Cloudera-JDBC-Connector-for-Apache-Impala-Release-Notes.txt
ClouderaImpalaJDBC-2.6.39.1073/docs/
ClouderaImpalaJDBC-2.6.39.1073/docs/Cloudera-JDBC-Connector-for-Apache-Impala-Release-Notes.pdf
ClouderaImpalaJDBC-2.6.39.1073/docs/Cloudera-JDBC-Connector-for-Apache-Impala-Release-Notes.txt
ClouderaImpalaJDBC-2.6.39.1073/docs/Cloudera-JDBC-Connector-for-Apache-Impala-Install-Guide.pdf
ClouderaImpalaJDBC-2.6.39.1073/docs/third-party-licenses.txt
ClouderaImpalaJDBC-2.6.39.1073/LeanImpalaJDBC42.jar
ClouderaImpalaJDBC-2.6.39.1073/ImpalaJDBC42.jar
ClouderaImpalaJDBC-2.6.39.1073/Cloudera-JDBC-Connector-for-Apache-Impala-Install-Guide.pdf
ClouderaImpalaJDBC-2.6.39.1073/EULA.txt
ClouderaImpalaJDBC-2.6.39.1073/third-party-licenses.txt{noformat}
Newer JDBC version 2.6.42.1076 still has the old layout that Impala tests
expect, which is good:
{noformat}
ClouderaImpalaJDBC-2.6.42.1076/Cloudera-JDBC-Connector-for-Apache-Impala-Release-Notes.txt
ClouderaImpalaJDBC-2.6.42.1076/docs/Cloudera-JDBC-Connector-for-Apache-Impala-Release-Notes.txt
ClouderaImpalaJDBC-2.6.42.1076/docs/Cloudera-JDBC-Connector-for-Apache-Impala-Release-Notes.pdf
ClouderaImpalaJDBC-2.6.42.1076/Cloudera-JDBC-Connector-for-Apache-Impala-Release-Notes.pdf
ClouderaImpalaJDBC-2.6.42.1076/docs/third-party-licenses.txt
ClouderaImpalaJDBC-2.6.42.1076/Software Quality Report for Impala JDBC
2.6.42.1076.pdf
ClouderaImpalaJDBC-2.6.42.1076/ClouderaImpalaJDBC42-2.6.42.1076/EULA.txt
ClouderaImpalaJDBC-2.6.42.1076/.DS_Store
ClouderaImpalaJDBC-2.6.42.1076/ClouderaImpalaJDBC42-2.6.42.1076/.DS_Store
ClouderaImpalaJDBC-2.6.42.1076/docs/Cloudera-JDBC-Connector-for-Apache-Impala-Install-Guide.pdf
ClouderaImpalaJDBC-2.6.42.1076/Cloudera-JDBC-Connector-for-Apache-Impala-Install-Guide.pdf
ClouderaImpalaJDBC-2.6.42.1076/ClouderaImpalaJDBC42-2.6.42.1076/libs/LeanImpalaJDBC42.jar
ClouderaImpalaJDBC-2.6.42.1076/ClouderaImpalaJDBC42-2.6.42.1076/ImpalaJDBC42.jar
ClouderaImpalaJDBC-2.6.42.1076/ClouderaImpalaJDBC-2.6.42.1076.zip
ClouderaImpalaJDBC-2.6.42.1076/ClouderaImpalaJDBC42-2.6.42.1076.zip{noformat}
> download-impala-jdbc-driver.sh fails
> ------------------------------------
>
> Key: IMPALA-15383
> URL: https://issues.apache.org/jira/browse/IMPALA-15383
> Project: IMPALA
> Issue Type: Bug
> Components: Infrastructure
> Reporter: Csaba Ringhofer
> Priority: Major
>
> example: https://jenkins.impala.io/job/ubuntu-20.04-dockerised-tests/5749/
> could reproduce locally, it seems that the structure of jdbc jars was changed
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
