[
https://issues.apache.org/jira/browse/CALCITE-4682?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17376915#comment-17376915
]
Julian Hyde commented on CALCITE-4682:
--------------------------------------
Can you please describe the "problem about cost of limit operator", as you see
it? Give a simple example where an operator gives the wrong cost.
> 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
> Priority: Major
>
> 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)
