[
https://issues.apache.org/jira/browse/IMPALA-12896?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17826869#comment-17826869
]
ASF subversion and git services commented on IMPALA-12896:
----------------------------------------------------------
Commit 6c0c26146d956ad771cee27283c1371b9c23adce in impala's branch
refs/heads/master from wzhou-code
[ https://gitbox.apache.org/repos/asf?p=impala.git;h=6c0c26146 ]
IMPALA-12896: Avoid JDBC table to be set as transactional table
In some deployment environment, JDBC tables are set as transactional
tables by default. This causes catalogd failed to load the metadata for
JDBC tables. This patch explicitly add table properties with
"transactional=false" for JDBC table to avoid the JDBC to be set as
transactional table.
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. Also adds Preconditions.check to make sure numNodes
equals 1 for DataSourceScanNode.
Updates FileSystemUtil.copyFileFromUriToLocal() function to write log
message for all types of exceptions.
Testing:
- Fixed planer tests for data source tables.
- Ran end-to-end tests of JDBC tables with query option
'exec_single_node_rows_threshold' as default value 100.
- Passed core-tests.
Change-Id: I556faeda923a4a11d4bef8c1250c9616f77e6fa6
Reviewed-on: http://gerrit.cloudera.org:8080/21141
Reviewed-by: Riza Suminto <riza.sumi...@cloudera.com>
Tested-by: Impala Public Jenkins <impala-public-jenk...@cloudera.com>
> 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
> Priority: Major
> Fix For: Impala 4.4.0
>
>
> 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)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-all-unsubscr...@impala.apache.org
For additional commands, e-mail: issues-all-h...@impala.apache.org
