[
https://issues.apache.org/jira/browse/IGNITE-25236?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aleksey Plekhanov updated IGNITE-25236:
---------------------------------------
Description:
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).
was: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. 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).
> 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
> Priority: Major
> Labels: calcite, ise
>
> 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)
