[
https://issues.apache.org/jira/browse/CALCITE-6109?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Julian Hyde resolved CALCITE-6109.
----------------------------------
Fix Version/s: 1.37.0
Resolution: Fixed
Fixed in
[b74c9344|https://github.com/apache/calcite/commit/b74c9344d3f6ee77f9a4c33db9a3095d60e73512];
thanks for the PR, [~xinqiu]!
> Avoid extra loops when optimizing statements with ternary expressions
> ---------------------------------------------------------------------
>
> Key: CALCITE-6109
> URL: https://issues.apache.org/jira/browse/CALCITE-6109
> Project: Calcite
> Issue Type: Improvement
> Components: linq4j
> Reporter: asdfgh19
> Assignee: asdfgh19
> Priority: Minor
> Labels: pull-request-available
> Fix For: 1.37.0
>
>
> {code:java}
> // org.apache.calcite.linq4j.tree.BlockBuilder#toBlock
> public BlockStatement toBlock() {
> if (optimizing && removeUnused) {
> // We put an artificial limit of 10 iterations just to prevent an endless
> // loop. Optimize should not loop forever, however it is hard to prove if
> // it always finishes in reasonable time.
> for (int i = 0; i < 10; i++) {
> if (!optimize(createOptimizeShuttle(), true)) {
> break;
> }
> }
> optimize(createFinishingOptimizeShuttle(), false);
> }
> return Expressions.block(statements);
> } {code}
> The above code comes from the org.apache.calcite.linq4j.tree.BlockBuilder
> class in the Calcite linq4j module.
> *1 What is the problem?*
> The problem is that for statements with ternary expressions, the for loop in
> the above code will always execute until the loop is exhausted, although it
> may not have done any optimization.
> *2 How to reproduce this problem？*
> We can reproduce the issue in the following ways.
> # Add some statements with ternary expressions to BlockBuilder through the
> BlockBuilder#add().
> # Call the BlockBuilder#toBlock() method.
> # Observe the for loop in the BlockBuilder#toBlock() method, which is always
> executed 10 times.
> *3 Why does this problem occur？*
> The reason is that when OptimizeShuttle traverses the statement, a new
> instance of TernaryExpression will always be created, regardless of whether
> the optimization is actually performed.
> This makes BlockBuilder mistakenly believe that this optimization is
> effective and start the next optimization.
> *4 What impact will this issue have?*
> This is a performance issue that’s hard to ignore.
> {code:java}
> return a != 1 ? b : c; {code}
> With a simple line of code like the above, the for loop in the
> org.apache.calcite.linq4j.tree.BlockBuilder#toBlock method will also be
> executed 10 times.
> If there are hundreds or thousands of statements in BlockBuilder#statements,
> this impact cannot be ignored.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
