Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

unexpected explain result _0 in the root operator. #14854

Closed
zz-jason opened this issue Feb 19, 2020 · 3 comments · Fixed by #15507
Closed

unexpected explain result _0 in the root operator. #14854

zz-jason opened this issue Feb 19, 2020 · 3 comments · Fixed by #15507
Assignees
Labels
good first issue Denotes an issue ready for a new contributor, according to the "help wanted" guidelines. help wanted Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines. severity/moderate sig/planner SIG: Planner type/bug The issue is confirmed as a bug.

Comments

@zz-jason
Copy link
Member

Bug Report

Please answer these questions before submitting your issue. Thanks!

1. What did you do?

as shown in #14852, the result of explain for connection is:

TiDB(root@127.0.0.1:test) > explain for connection 1;
+-------------------------+-------+------+-----------------------------------------+
| id                      | count | task | operator info                           |
+-------------------------+-------+------+-----------------------------------------+
| _0                      | N/A   | root | N/A                                     |
| └─Batch_Point_Get_1     | 2.00  | root | table:bmsql_item, handles: %#v[123 456] |
+-------------------------+-------+------+-----------------------------------------+
2 rows in set (0.00 sec)

it outputs a _0 operator as the root operator, which is unexpected.

2. What did you expect to see?

disappear from the result

3. What did you see instead?

as described in the above.

4. What version of TiDB are you using (tidb-server -V or run select tidb_version(); on TiDB)?

the same as #14852

@zz-jason zz-jason added type/bug The issue is confirmed as a bug. help wanted Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines. labels Feb 19, 2020
@sre-bot
Copy link
Contributor

sre-bot commented Feb 20, 2020

Dear contributor, the first Performance challenge program has been closed. But you can still contribute to this issue and we appreciate your contribution.

@zz-jason zz-jason added the good first issue Denotes an issue ready for a new contributor, according to the "help wanted" guidelines. label Feb 20, 2020
@sre-bot
Copy link
Contributor

sre-bot commented Feb 20, 2020

Dear contributor, the first Performance challenge program has been closed. But you can still contribute to this issue and we appreciate your contribution.

@zz-jason zz-jason added the sig/planner SIG: Planner label Mar 9, 2020
@zz-jason
Copy link
Member Author

@LittleFall PTAL

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
good first issue Denotes an issue ready for a new contributor, according to the "help wanted" guidelines. help wanted Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines. severity/moderate sig/planner SIG: Planner type/bug The issue is confirmed as a bug.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants