Update query-execution-plan.md #3359

ireneontheway · 2020-07-21T10:22:13Z

What is changed, added or deleted? (Required)

Update the documentation for query-execution-plan.md

Which TiDB version(s) do your changes apply to? (Required)

What is the related PR or file link(s)?

This PR is translated from: perf-tuning: Update the doc of query-execution-plan docs-cn#3201 , part of pingcap/docs-cn#3170
Other reference link(s):

Do your changes match any of the following descriptions?

Delete files
Change aliases
Have version specific changes
Might cause conflicts

ireneontheway · 2020-07-21T10:23:16Z

/label size/medium,special-week,needs-cherry-pick-4.0,translation/from-docs-cn

ireneontheway · 2020-07-21T10:29:04Z

PTAL @yikeke

ireneontheway · 2020-07-21T10:50:39Z

/cc yikeke

ireneontheway · 2020-07-21T10:55:35Z

/cc Reminiscent

yikeke · 2020-07-21T11:04:07Z

/cc zz-jason

query-execution-plan.md

ran-huang · 2020-07-22T04:03:00Z

query-execution-plan.md

+
+In the IndexMerge access mode, the optimizer can use multiple indexes in a table, and combine the returned results of each index to generate the execution plan of the latter IndexMerge in the figure above. Here the `IndexMerge_16` operator has three child nodes, among which `IndexRangeScan_13` and `IndexRangeScan_14` get all the `RowID`s that meet the conditions based on the result of range scan, and then the `TableRowIDScan_15` operator accurately reads all the data that meet the conditions according to these `RowID`s.
+
+For the table scan that is performed by range such as indexRangeScan/TableRangeScan , the operator info column in the explain table has more information about the range of the scanned data than other scan operations. In the above example, the `range:(1,+inf]` in the IndexRangeScan operator indicates that the operator scans the data from 1 to positive infinity.


其中对于 IndexRangeScan/TableRangeScan 一类按范围进行的扫表操作来说，explain 表中 operator info 列相比于其他扫表操作，多了被扫描数据的范围这一信息
@zz-jason PTAL. 这一句原文表达不太清晰，是指把 operator info 列和其他扫表操作进行比较吗？还是把 IndexRangeScan/TableRangeScan 和其他扫表操作进行比较呢？

是 xxxRangeScan 和其他扫表（Scan）操作进行比较。现在扫表操作总共有这些：

IndexRangeScan

IndexFullScan

TableRangeScan

TableFullScan

TableRowIDScan

@ireneontheway 请对应修改英文，谢谢～

query-execution-plan.md

ran-huang · 2020-07-22T04:33:02Z

I just found that most of the changes can be copied from index-merge.md 🤔
@ireneontheway Could you please check this file and align some expressions? I think we'd better make use of the existing translation.

Co-authored-by: Ran <[email protected]>

ireneontheway · 2020-07-23T05:27:40Z

PTAL @ran-huang

zz-jason · 2020-07-24T08:08:42Z

query-execution-plan.md

+
+In the IndexMerge access mode, the optimizer can use multiple indexes in a table, and combine the returned results of each index to generate the execution plan of the latter IndexMerge in the figure above. Here the `IndexMerge_16` operator has three child nodes, among which `IndexRangeScan_13` and `IndexRangeScan_14` get all the `RowID`s that meet the conditions based on the result of range scan, and then the `TableRowIDScan_15` operator accurately reads all the data that meet the conditions according to these `RowID`s.
+
+For the table scan that is performed by range such as indexRangeScan/TableRangeScan , the operator info column in the explain table has more information about the range of the scanned data than other scan operations. In the above example, the `range:(1,+inf]` in the IndexRangeScan operator indicates that the operator scans the data from 1 to positive infinity.


是 xxxRangeScan 和其他扫表（Scan）操作进行比较。现在扫表操作总共有这些：

IndexRangeScan

IndexFullScan

TableRangeScan

TableFullScan

TableRowIDScan

query-execution-plan.md

Co-authored-by: Zhang Jian <[email protected]>

ran-huang · 2020-07-24T10:54:34Z

@ireneontheway To align with pingcap/docs-cn#3201, please also delete index-merge.md and remove the link from TOC.md

ran-huang

LGTM

yikeke · 2020-07-27T03:35:12Z

index-merge.md

---
-title: Access Tables Using `IndexMerge`
-summary: Learn how to access tables using the `IndexMerge` query execution plan.
-aliases: ['/docs/dev/index-merge/','/docs/dev/reference/performance/index-merge/']


Please add the following aliases into https://github.com/pingcap/docs/pull/3359/files#diff-7958dda55af6cba3f29e9e06ddd9d583R4:

'/docs/dev/index-merge/','/docs/dev/reference/performance/index-merge/','/tidb/dev/index-merge' @ireneontheway

Please note: When we delete a file, in most cases, we need to add an alias to another document to redirect the old URLs. @ireneontheway @ran-huang

To fix pingcap/docs-cn#3201, please help add the missing aliases to query-execution-plan.md in the docs-cn repo. @ireneontheway

query-execution-plan.md

Co-authored-by: Keke Yi <[email protected]>

yikeke

LGTM

zz-jason

LGTM

Signed-off-by: ti-srebot <[email protected]>

ti-srebot · 2020-07-27T09:49:49Z

cherry pick to release-4.0 in PR #3427

* cherry pick #3359 to release-4.0 Signed-off-by: ti-srebot <[email protected]> * Update query-execution-plan.md * Update query-execution-plan.md * Update query-execution-plan.md * Delete index-merge.md Co-authored-by: ireneontheway <[email protected]> Co-authored-by: ireneontheway <[email protected]>

This reverts commit 6737794.

Update query-execution-plan.md

3120a92

ti-srebot added needs-cherry-pick-4.0 size/medium Changes of a medium size. special-week PR from Document Special Week. translation/from-docs-cn This PR is translated from a PR in pingcap/docs-cn. labels Jul 21, 2020

Update query-execution-plan.md

8d13845

Update query-execution-plan.md

8f59ca0

ti-srebot requested a review from yikeke July 21, 2020 10:50

ti-srebot requested review from ChenPeng2013 and removed request for ChenPeng2013 July 21, 2020 10:58

ti-srebot requested a review from zz-jason July 21, 2020 11:04

yikeke requested review from ran-huang and removed request for yikeke July 22, 2020 02:49

ran-huang reviewed Jul 22, 2020

View reviewed changes

ireneontheway and others added 4 commits July 23, 2020 12:54

Apply suggestions from code review

62ccdfc

Co-authored-by: Ran <[email protected]>

Update query-execution-plan.md

0cffb12

Co-authored-by: Ran <[email protected]>

Update query-execution-plan.md

d79b068

Update query-execution-plan.md

7aeaa9d

zz-jason reviewed Jul 24, 2020

View reviewed changes

Update query-execution-plan.md

5ea618e

Co-authored-by: Zhang Jian <[email protected]>

ireneontheway added 2 commits July 27, 2020 10:07

align with pingcap/docs-cn#3201

19b408c

Update whats-new-in-tidb-4.0.md

e7fdade

Merge branch 'master' into query-execution-plan

b668835

ran-huang approved these changes Jul 27, 2020

View reviewed changes

ti-srebot added the status/LGT1 Indicates that a PR has LGTM 1. label Jul 27, 2020

yikeke reviewed Jul 27, 2020

View reviewed changes

yikeke added the requires-version-specific-changes After cherry-picked, the cherry-picked PR requires further changes. label Jul 27, 2020

Update query-execution-plan.md

fcdfa06

yikeke reviewed Jul 27, 2020

View reviewed changes

query-execution-plan.md Outdated Show resolved Hide resolved

yikeke reviewed Jul 27, 2020

View reviewed changes

query-execution-plan.md Outdated Show resolved Hide resolved

Apply suggestions from code review

729e2af

Co-authored-by: Keke Yi <[email protected]>

yikeke approved these changes Jul 27, 2020

View reviewed changes

ti-srebot removed the status/LGT1 Indicates that a PR has LGTM 1. label Jul 27, 2020

ti-srebot approved these changes Jul 27, 2020

View reviewed changes

ti-srebot added the status/LGT2 Indicates that a PR has LGTM 2. label Jul 27, 2020

Merge branch 'master' into query-execution-plan

eedd585

zz-jason approved these changes Jul 27, 2020

View reviewed changes

ti-srebot added status/LGT3 The PR has already had 3 LGTM. and removed status/LGT2 Indicates that a PR has LGTM 2. labels Jul 27, 2020

ireneontheway merged commit 2e2916f into pingcap:master Jul 27, 2020

ti-srebot pushed a commit to ti-srebot/docs that referenced this pull request Jul 27, 2020

cherry pick pingcap#3359 to release-4.0

006940e

Signed-off-by: ti-srebot <[email protected]>

ti-srebot mentioned this pull request Jul 27, 2020

Update query-execution-plan.md (#3359) #3427

Merged

9 tasks

ireneontheway added a commit that referenced this pull request Jul 27, 2020

Revert "Update query-execution-plan.md (#3359) (#3427)"

82c8b09

This reverts commit 6737794.

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Update query-execution-plan.md #3359

Update query-execution-plan.md #3359

ireneontheway commented Jul 21, 2020 •

edited by yikeke

Loading

ireneontheway commented Jul 21, 2020

ireneontheway commented Jul 21, 2020

ireneontheway commented Jul 21, 2020

ireneontheway commented Jul 21, 2020

yikeke commented Jul 21, 2020

ran-huang Jul 22, 2020

zz-jason Jul 24, 2020

ran-huang Jul 24, 2020

ran-huang commented Jul 22, 2020

ireneontheway commented Jul 23, 2020

zz-jason Jul 24, 2020

ran-huang commented Jul 24, 2020

ran-huang left a comment

yikeke Jul 27, 2020

yikeke Jul 27, 2020

yikeke Jul 27, 2020

yikeke left a comment

zz-jason left a comment

ti-srebot commented Jul 27, 2020


		In the IndexMerge access mode, the optimizer can use multiple indexes in a table, and combine the returned results of each index to generate the execution plan of the latter IndexMerge in the figure above. Here the `IndexMerge_16` operator has three child nodes, among which `IndexRangeScan_13` and `IndexRangeScan_14` get all the `RowID`s that meet the conditions based on the result of range scan, and then the `TableRowIDScan_15` operator accurately reads all the data that meet the conditions according to these `RowID`s.

		For the table scan that is performed by range such as indexRangeScan/TableRangeScan , the operator info column in the explain table has more information about the range of the scanned data than other scan operations. In the above example, the `range:(1,+inf]` in the IndexRangeScan operator indicates that the operator scans the data from 1 to positive infinity.

Update query-execution-plan.md #3359

Update query-execution-plan.md #3359

Conversation

ireneontheway commented Jul 21, 2020 • edited by yikeke Loading

What is changed, added or deleted? (Required)

Which TiDB version(s) do your changes apply to? (Required)

What is the related PR or file link(s)?

Do your changes match any of the following descriptions?

ireneontheway commented Jul 21, 2020

ireneontheway commented Jul 21, 2020

ireneontheway commented Jul 21, 2020

ireneontheway commented Jul 21, 2020

yikeke commented Jul 21, 2020

ran-huang Jul 22, 2020

Choose a reason for hiding this comment

zz-jason Jul 24, 2020

Choose a reason for hiding this comment

ran-huang Jul 24, 2020

Choose a reason for hiding this comment

ran-huang commented Jul 22, 2020

ireneontheway commented Jul 23, 2020

zz-jason Jul 24, 2020

Choose a reason for hiding this comment

ran-huang commented Jul 24, 2020

ran-huang left a comment

Choose a reason for hiding this comment

yikeke Jul 27, 2020

Choose a reason for hiding this comment

yikeke Jul 27, 2020

Choose a reason for hiding this comment

yikeke Jul 27, 2020

Choose a reason for hiding this comment

yikeke left a comment

Choose a reason for hiding this comment

zz-jason left a comment

Choose a reason for hiding this comment

ti-srebot commented Jul 27, 2020

ireneontheway commented Jul 21, 2020 •

edited by yikeke

Loading