[
https://issues.apache.org/jira/browse/IGNITE-24642?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17931229#comment-17931229
]
Ignite TC Bot commented on IGNITE-24642:
----------------------------------------
{panel:title=Branch: [pull/11899/head] Base: [master] : No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
{panel:title=Branch: [pull/11899/head] Base: [master] : No new tests
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}{panel}
[TeamCity *--> Run :: All*
Results|https://ci2.ignite.apache.org/viewLog.html?buildId=8329384&buildTypeId=IgniteTests24Java8_RunAll]
> Calcite do not trim tables in case of multiple joins
> ----------------------------------------------------
>
> Key: IGNITE-24642
> URL: https://issues.apache.org/jira/browse/IGNITE-24642
> Project: Ignite
> Issue Type: Bug
> Reporter: Maksim Timonin
> Assignee: Maksim Timonin
> Priority: Major
> Labels: ise
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> IgnitePlanner#trimUnusuedFields do not trim fields in case query contains two
> or more joins.
> Comment that describes this logic looks weird, as trims applies on
> PROJECT_PUSH_DOWN to IgniteLogicalTableScan and do not produce new leafs.
> Let's remove this condition, as it affects peformance
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
