Description
Please search the existing issues for relevant feature requests, add upvotes to pre-existing requests.
Feature Description
TiDB use its own plan format.
explain select c_id from customer where c_city='8VM4rH5e6lUfZAqMFU';
+---------------------------+-----------+-----------+----------------+----------------------------------------------------+
| id | estRows | task | access object | operator info |
+---------------------------+-----------+-----------+----------------+----------------------------------------------------+
| Projection_4 | 1.00 | root | | onlinedb.customer.c_id |
| └─TableReader_7 | 1.00 | root | | data:Selection_6 |
| └─Selection_6 | 1.00 | cop[tikv] | | eq(onlinedb.customer.c_city, "8VM4rH5e6lUfZAqMFU") |
| └─TableFullScan_5 | 100000.00 | cop[tikv] | table:customer | keep order:false |
+---------------------------+-----------+-----------+----------------+----------------------------------------------------+
4 rows in set (0.00 sec)
but SOAR use MySQL style plan format.When SOAR analyze the SQL statement running on TiDB , all of the explain information filled with NULL.
| id | select_type | table | partitions | type | possible_keys | key | key_len | ref | rows | filtered | scalability | Extra |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 0 | NULL | NULL | NULL | NULL | NULL | NULL | NULL | NULL | 0 | 0.00% | ☠️ O(n) | NULL |
| 0 | NULL | NULL | NULL | NULL | NULL | NULL | NULL | NULL | 0 | 0.00% | ☠️ O(n) | NULL |
| 0 | NULL | NULL | NULL | NULL | NULL | NULL | NULL | NULL | 0 | 0.00% | ☠️ O(n) | NULL |
| 0 | NULL | NULL | NULL | NULL | NULL | NULL | NULL | NULL | 0 | 0.00% | ☠️ O(n) | NULL |
Use Case(s)
Any user wants to tune the TiDB SQL performance by using SOAR.
Is any plan about the explain information compatible with TiDB explain plan.