Details
-
Bug
-
Status: Resolved
-
Blocker
-
Resolution: Duplicate
-
Impala 4.4.0
-
ghx-label-6
Description
The query_test.test_ext_data_sources.TestExtDataSources hits failures on S3 and Ozone. The failure in test_verify_jdbc_table_properties is due to the different paths:
query_test/test_ext_data_sources.py:68: in test_verify_jdbc_table_properties assert properties['__IMPALA_DATA_SOURCE_LOCATION'] == \ E assert 'ofs://localh...ta-source.jar' == 'hdfs://localh...ta-source.jar' E - ofs://localhost:9862/impala/test-warehouse/data-sources/jdbc-data-source.jar E ? ^ --- ^^^^^^^ E + hdfs://localhost:20500/test-warehouse/data-sources/jdbc-data-source.jar E ? ^^
The failure in test_jdbc_data_source is different for Ozone vs S3:
S3: beeswax/impala_beeswax.py:390: in wait_for_finished raise ImpalaBeeswaxException("Query aborted:" + error_log, None) E ImpalaBeeswaxException: ImpalaBeeswaxException: E Query aborted:Caught exception while trying to execute query:Cannot create PoolableConnectionFactory (FATAL: database "functional" does not exist) Ozone: beeswax/impala_beeswax.py:390: in wait_for_finished raise ImpalaBeeswaxException("Query aborted:" + error_log, None) E ImpalaBeeswaxException: ImpalaBeeswaxException: E Query aborted:Caught exception while trying to execute query:org.apache.impala.extdatasource.jdbc.exception.JdbcDatabaseAccessException: Unable to cache jdbc driver jar at location '/test-warehouse/data-sources/jdbc-drivers/postgresql-jdbc.jar'. Check that the file exists and is readable. Message: [Failed to get file info /test-warehouse/data-sources/jdbc-drivers/postgresql-jdbc.jar E Error(2): No such file or directory]
Depending on how related these are, the different failures may need to be split out.
Introduce in IMPALA-5741 (https://github.com/apache/impala/commit/c2bd30a1b3b49ccc7770ec5ab4adeb0b75f40240)
Attachments
Issue Links
- duplicates
-
IMPALA-12470 Support different schemes for jdbc driver url when creating external jdbc table
- Resolved