You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Aleksey Plekhanov (Jira)" <ji...@apache.org> on 2025/06/11 08:02:00 UTC

[jira] [Resolved] (IGNITE-25236) Calcite engine. Excessive log output on planning error

     [ https://issues.apache.org/jira/browse/IGNITE-25236?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Aleksey Plekhanov resolved IGNITE-25236.
----------------------------------------
    Fix Version/s: 2.18
     Release Note: SQL Calcite: Fixed excessive log output on planning error
       Resolution: Fixed

[~vladnovoren], looks good to me. Merged to master. Thanks for the contribution!

> Calcite engine. Excessive log output on planning error
> ------------------------------------------------------
>
>                 Key: IGNITE-25236
>                 URL: https://issues.apache.org/jira/browse/IGNITE-25236
>             Project: Ignite
>          Issue Type: Improvement
>            Reporter: Aleksey Plekhanov
>            Assignee: Vladislav Novikov
>            Priority: Major
>              Labels: calcite, ise
>             Fix For: 2.18
>
>          Time Spent: 50m
>  Remaining Estimate: 0h
>
> In case of planning error (for example, when there are no valid plans where found during planning timeout) calcite engine throws full dump of planner to the log:
> {noformat}
> Original rel:
> ...
> Sets:
> ...
> Graphviz:
> ...
> {noformat}
> This dump sometimes exceeds hundreds of megabytes and in most cases is useless for users. We should reduce amount of data written to the log in case of planning error (perhaps dump internals only when {{calcite.debug}} property is set).



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