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

Posted to dev@calcite.apache.org by "ZiLin Chen (Jira)" <ji...@apache.org> on 2021/07/07 07:00:00 UTC

[jira] [Created] (CALCITE-4682) Cost of Operator limit may break cumulative cost calculation assumption

ZiLin Chen created CALCITE-4682:
-----------------------------------

             Summary: Cost of Operator limit may break cumulative cost calculation assumption
                 Key: CALCITE-4682
                 URL: https://issues.apache.org/jira/browse/CALCITE-4682
             Project: Calcite
          Issue Type: Improvement
          Components: core
            Reporter: ZiLin Chen


Any way calcite can provide to solve the problem about cost of limit operator?

Limit operator can affect how the join below to choose specific algorithm by start up cost instead of cumulative cost.

However volcano planner can only deal with the total cost, which works well in OLAP system, but OLTP system need some kind of cost model to solve this problem.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)