[
https://issues.apache.org/jira/browse/CALCITE-7164?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gustavo de Morais updated CALCITE-7164:
---------------------------------------
Description:
The MultiJoin node currently doesn't support hints. This means that when we
convert a set of joins to a MultiJoin, the hints are lost and will not be
applied. For the currently implemented rules, the reordering rules convert
joins into a MultiJoin and do not pass down the the STATE TTL hints since it
doesn't contain that property, which leads to it being lost.
It'd be good to have the hints property added to the MultiJoin node so that we
can preserve the hints coming from each join. Additionally, we have to update
the current optimizer rules that operate on MultiJoin to pass down this
property so it's not lost. Optimally, we could use a MultiJoin.copy method
instead of instantiating a new class every time so all rules don't have to be
updated on a change like this.
was:
The MultiJoin node currently doesn't support hints. This means that when we
convert a set of joins to a MultiJoin, the hints are lost and will not be
applied. Specifically for the currently implemented rules, the currently
reordering rules cause the STATE TTL hints to be lost.
It'd be good to have the hints property added to the MultiJoin node so that we
can preserve the hints coming from each join. Additionally, we have to update
the current optimizer rules that operate on MultiJoin to pass down this
property so it's not lost. Optimally, we could use a MultiJoin.copy method
instead of instantiating a new class every time so all rules don't have to be
updated on a change like this.
> Support hints for MultiJoin
> ---------------------------
>
> Key: CALCITE-7164
> URL: https://issues.apache.org/jira/browse/CALCITE-7164
> Project: Calcite
> Issue Type: Improvement
> Reporter: Gustavo de Morais
> Priority: Major
>
> The MultiJoin node currently doesn't support hints. This means that when we
> convert a set of joins to a MultiJoin, the hints are lost and will not be
> applied. For the currently implemented rules, the reordering rules convert
> joins into a MultiJoin and do not pass down the the STATE TTL hints since it
> doesn't contain that property, which leads to it being lost.
> It'd be good to have the hints property added to the MultiJoin node so that
> we can preserve the hints coming from each join. Additionally, we have to
> update the current optimizer rules that operate on MultiJoin to pass down
> this property so it's not lost. Optimally, we could use a MultiJoin.copy
> method instead of instantiating a new class every time so all rules don't
> have to be updated on a change like this.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
