[
https://issues.apache.org/jira/browse/IGNITE-16151?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17464011#comment-17464011
]
Valentin Kulichenko commented on IGNITE-16151:
----------------------------------------------
[~ivandasch] I would suggest to have a single timeout for the query execution
as a whole.
>From the user's perspective, planning is a part of execution. There is no good
>way for a user to decide how long the planning should take.
> Introduce timeout for calcite planner
> -------------------------------------
>
> Key: IGNITE-16151
> URL: https://issues.apache.org/jira/browse/IGNITE-16151
> Project: Ignite
> Issue Type: Improvement
> Components: sql
> Reporter: Ivan Daschinsky
> Priority: Major
> Labels: calcite, calcite2-required, calcite3-required
>
> Since it is quite common case that calcite planner can produce too many plans
> and can planning infinitely, it is of crucial
> importance to be able to cancel this process on timeout.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
