[
https://issues.apache.org/jira/browse/CALCITE-4290?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17214727#comment-17214727
]
Stamatis Zampetakis commented on CALCITE-4290:
----------------------------------------------
Hey [~rrrrrr111], you may find something useful in the following links:
https://lists.apache.org/thread.html/re6bb7e4db4b71296dba164ca2784efdec5b925105af0aa8f02cd3f5f%40%3Cdev.calcite.apache.org%3E
https://lists.apache.org/thread.html/4d4019b01a9dec08467204baaf0a50f8f516241357a3e881fdde022e%40%3Cdev.calcite.apache.org%3E
https://github.com/zabetak/calcite/commit/c7646fa6d3054b9e6b9a800e08d18f3cc89922e4
> 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)
