-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
planner: add the doc for hint #13313
Conversation
[REVIEW NOTIFICATION] This pull request has been approved by:
To complete the pull request process, please ask the reviewers in the list to review by filling The full list of commands accepted by this bot can be found here. Reviewer can indicate their review by submitting an approval review. |
Co-authored-by: TomShawn <41534398+TomShawn@users.noreply.github.com>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
system-variables.md
Outdated
|
||
> **注意:** | ||
> | ||
> v6.7.0 之前的版本行为和该变量设置为 'OFF' 的行为一致。因此当从老版本升级到新版本时一些行为会发生变化,主要是 join 的连接顺序。如果有不符合预期的情况,可以通过将该参数设置为 'OFF' 的方式或者通过使用 `LEADING()` hint 的方式进行规避,强烈推荐使用后一种方式。 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
升级默认保持在OFF
比较好。
rest LGTM |
Co-authored-by: Roger Song <roger.song@pingcap.com>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
system-variables.md
Outdated
- 是否持久化到集群:是 | ||
- 类型:布尔型 | ||
- 默认值:`ON` | ||
- 这个变量用来控制 join method hint 是否会影响 join reorder 的优化过程,包括 `LEADING()` hint 的使用。默认值为 `ON`,即默认不影响。如果设置为 `OFF`,在一些同时使用 join method hint 和 `LEADING()` hint 的场景下会有冲突产生。 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
- 这个变量用来控制 join method hint 是否会影响 join reorder 的优化过程,包括 `LEADING()` hint 的使用。默认值为 `ON`,即默认不影响。如果设置为 `OFF`,在一些同时使用 join method hint 和 `LEADING()` hint 的场景下会有冲突产生。 | |
- 这个变量用来控制 join method hint 是否会影响 join reorder 的优化过程,包括 [`LEADING()` hint](/optimizer-hints.md#leadingt1_name--tl_name-) 的使用。默认值为 `ON`,即默认不影响。如果设置为 `OFF`,在一些同时使用 join method hint 和 `LEADING()` hint 的场景下会有冲突产生。 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
这里是否要解释下哪些 hint 属于 join method hint?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
可以解释,不过有点多,是举个例子还是需要多列出来。
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
至少举一个例子吧。optimizer-hint 这篇文档里也没有提过哪些属于 join method hint,可能会有一点定义不清晰
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
update. PTAL @ran-huang
Co-authored-by: Ran <huangran.alex@gmail.com>
Co-authored-by: Ran <huangran.alex@gmail.com>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Rest LGTM
Co-authored-by: Aolin <aolinz@outlook.com>
Co-authored-by: Aolin <aolinz@outlook.com>
Co-authored-by: Aolin <aolinz@outlook.com>
Co-authored-by: Aolin <aolinz@outlook.com>
Update. PTAL @Oreoxmt |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Rest LGTM
Co-authored-by: Aolin <aolinz@outlook.com>
/merge |
This pull request has been accepted and is ready to merge. Commit hash: 6c3d771
|
First-time contributors' checklist
What is changed, added or deleted? (Required)
Which TiDB version(s) do your changes apply to? (Required)
Tips for choosing the affected version(s):
By default, CHOOSE MASTER ONLY so your changes will be applied to the next TiDB major or minor releases. If your PR involves a product feature behavior change or a compatibility change, CHOOSE THE AFFECTED RELEASE BRANCH(ES) AND MASTER.
For details, see tips for choosing the affected versions (in Chinese).
What is the related PR or file link(s)?
Do your changes match any of the following descriptions?