In non-explain queries, optimizer trace is flooded with join_execution nodes

      "join_execution": {

        "select_id": 1,

        "steps": [

          {

            "join_execution": {

              "select_id": 2,

              "steps": []

            }

          },

          {

            "join_execution": {

              "select_id": 2,

              "steps": []

            }

          }

          ...

create table t1 (a int, b int);

insert into t1 values (1, 999),(999, 1),(987,987);

create table t2 (a int, b int, index(a),index(b));

insert into t2 select seq, seq from seq_1_to_1000;

set optimizer_trace=1;

analyze format=json 

select * 

from 

  t1, t2

where

  t2.a<t1.a and t2.b<t1.b;

select * from information_schema.optimizer_trace;

   ... 

      "join_execution": {

        "select_id": 1,

        "steps": [

          {

            "table": "t2",

            "range_analysis": { ... }

          }

          {

            "table": "t2",

            "range_analysis": { ... }

          }

          {

            "table": "t2",

            "range_analysis": { ... }

          }