You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@flink.apache.org by "Gustavo de Morais (Jira)" <ji...@apache.org> on 2025/10/23 20:42:00 UTC

[jira] [Created] (FLINK-38554) Adjust FlinkMultiJoin self cost to be more accurate

Gustavo de Morais created FLINK-38554:
-----------------------------------------

             Summary: Adjust FlinkMultiJoin self cost to be more accurate
                 Key: FLINK-38554
                 URL: https://issues.apache.org/jira/browse/FLINK-38554
             Project: Flink
          Issue Type: Sub-task
          Components: Table SQL / Planner
    Affects Versions: 2.1.0
            Reporter: Gustavo de Morais
            Assignee: Gustavo de Morais
             Fix For: 2.2.0


We've observed some situations where the volcano planner is picking a less efficient plan out of LOGICAL_OPT_RULES.

This seems to be mapped down to us hitting the 
DOUBLE max value for some of metrics. The consequence is that the cost of the nodes past the MultiJoin does not add up to the cumulative cost which leads to the issue above.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)