[
https://issues.apache.org/jira/browse/IGNITE-25236?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17959656#comment-17959656
]
Ignite TC Bot commented on IGNITE-25236:
----------------------------------------
{panel:title=Branch: [pull/12047/head] Base: [master] : No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
{panel:title=Branch: [pull/12047/head] Base: [master] : New Tests
(1)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}
{color:#00008b}Calcite SQL{color} [[tests
1|https://ci2.ignite.apache.org/viewLog.html?buildId=8474719]]
* {color:#013220}IgniteCalciteTestSuite:
CalcitePlanningDumpTest.testTruncatedCalciteDump - PASSED{color}
{panel}
[TeamCity *--> Run :: All*
Results|https://ci2.ignite.apache.org/viewLog.html?buildId=8474804&buildTypeId=IgniteTests24Java8_RunAll]
> 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
> Time Spent: 0.5h
> 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)
