[
https://issues.apache.org/jira/browse/IGNITE-16151?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17464461#comment-17464461
]
Ivan Daschinsky commented on IGNITE-16151:
------------------------------------------
[~vkulichenko] I understand you concern, but unfortunately this ticket is about
interruption of query in planning phase. We cannot wait for a long timeout,
because planner
produces too many plans and it can lead to out of memory. Moreover, thread that
starts query is effectively hanging. We should terminate this ASAP, within few
seconds.
May be user should not be able to set this timeout at all, just may be system
property.
> 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)
