You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues-all@impala.apache.org by "Kurt Deschler (Jira)" <ji...@apache.org> on 2024/10/01 13:42:00 UTC
[jira] [Commented] (IMPALA-12909) Generate distributed plan for query accessing multiple JDBC tables
[ https://issues.apache.org/jira/browse/IMPALA-12909?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17886176#comment-17886176 ]
Kurt Deschler commented on IMPALA-12909:
----------------------------------------
Has any though been given on how to partition rows for the executors?
> Generate distributed plan for query accessing multiple JDBC tables
> ------------------------------------------------------------------
>
> Key: IMPALA-12909
> URL: https://issues.apache.org/jira/browse/IMPALA-12909
> Project: IMPALA
> Issue Type: Sub-task
> Components: Frontend
> Reporter: Wenzhe Zhou
> Assignee: Pranav Yogi Lodha
> Priority: Major
>
> For a query which access multiple JDBC tables, Planner generate single node plan. It's better to generate distributed plan so that JDBC read could be scheduled on executors. This restriction is due to current design of External data source framework because scan is single threaded. DataSourceScanNode cannot run in node other than coordinator.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-all-unsubscribe@impala.apache.org
For additional commands, e-mail: issues-all-help@impala.apache.org