Wenzhe Zhou created IMPALA-12896:
------------------------------------
Summary: Avoid JDBC table to be set as transactional table
Key: IMPALA-12896
URL: https://issues.apache.org/jira/browse/IMPALA-12896
Project: IMPALA
Issue Type: Sub-task
Components: Frontend
Reporter: Wenzhe Zhou
Assignee: Wenzhe Zhou
Found following issues in downstream integration.
1) JDBC tables created in some deployment environment were set as transactional
tables by default. This caused catalogd failed to load the metadata for JDBC
tables. We have to explicitly set table properties with "transactional=false"
for JDBC tables.
2) FileSystemUtil.copyFileFromUriToLocal() function wrote log message only for
IOException. We should write log message for all types of exceptions so that we
can captures errors which caused failures to load JDBC drivers.
3) The operations on JDBC table are processed only on coordinator. The
processed rows should be estimated as 0 for DataSourceScanNode by planner so
that coordinator-only query plans are generated for simple queries on JDBC
tables and queries could be executed without invoking executor nodes.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
