Joe McDonnell created IMPALA-14545:
--------------------------------------
Summary: S3PlannerTest.testDataSourceTables fails with "Failed to
copy JDBC driver"
Key: IMPALA-14545
URL: https://issues.apache.org/jira/browse/IMPALA-14545
Project: IMPALA
Issue Type: Bug
Components: Infrastructure, Test
Affects Versions: Impala 5.0.0
Reporter: Joe McDonnell
Assignee: Pranav Yogi Lodha
S3PlannerTest.testDataSourceTables is failing on S3 jobs with:
{noformat}
Query:
select * from functional.jdbc_decimal_tbl where d3 > 123.456 and d5 < 10.0
Error Stack:
org.apache.impala.common.InternalException: Data source
DataSource{name=impalajdbcdatasource, location=,
className=org.apache.impala.extdatasource.jdbc.JdbcDataSource, apiVersion=V1}
returned an error from prepare(): Failed to retrieve total number of records:
Failed to copy JDBC driver from
'hdfs://localhost:20500/test-warehouse/data-sources/jdbc-drivers/postgresql-jdbc.jar'
to local filesystem.{noformat}
This seems to have started when IMPALA-13661 merged, but it is unclear why it
started failing then.
[https://github.com/apache/impala/commit/a77fec6391eaf5db7c52000c7446cc8582c770ac]
I think the main problem for this is in the paths used in
[https://github.com/apache/impala/blob/master/testdata/bin/create-ext-data-source-table.sql]
. There are two main problems:
1. Some of the paths are absolute (e.g.
[https://github.com/apache/impala/blob/master/testdata/bin/create-ext-data-source-table.sql#L90]
)
2. The paths make no allowance for a FILESYSTEM_PREFIX or WAREHOUSE_PREFIX.
Fixing the first one should fix S3. Since we don't run frontend tests on other
non-HDFS filesystems, the second may not matter for this test.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
