[
https://issues.apache.org/jira/browse/CALCITE-4290?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17210876#comment-17210876
]
Roman Churganov commented on CALCITE-4290:
------------------------------------------
This problem can be reproduced on pure Calcite without any custom changes to a
query plan, I can provide code example if needed, so do you have any plans to
fix this?
> Not optimal subqueries due to a "*" in them
> -------------------------------------------
>
> Key: CALCITE-4290
> URL: https://issues.apache.org/jira/browse/CALCITE-4290
> Project: Calcite
> Issue Type: Bug
> Components: jdbc-adapter
> Affects Versions: 1.25.0
> Reporter: Roman Churganov
> Priority: Major
>
> Run a query which should be distributed into sub-queries onto multiple
> schemas through JDBC adapter, for example
> select ft.id, ft.c11, tt.c41 from sch1.foo ft join sch2.tab tt on
> ft.id = tt.id
> Calcite will make two sub-queries like SELECT * FROM "TAB" ORDER BY "ID" and
> SELECT * FROM "FOO" ORDER BY "ID" which are not optimal due to an excessive
> columns data requested
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
