- 
                Notifications
    You must be signed in to change notification settings 
- Fork 706
planner: Add subquery variables #21943
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
base: master
Are you sure you want to change the base?
Conversation
| [APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: The full list of commands accepted by this bot can be found here. 
Needs approval from an approver in each of these files:
 Approvers can indicate their approval by writing  | 
| Summary of ChangesHello @terry1purcell, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed! This pull request updates the system variables documentation to include two new variables,  Highlights
 Using Gemini Code AssistThe full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips. Invoking Gemini You can request assistance from Gemini at any point by creating a comment using either  
 Customization To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a  Limitations & Feedback Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here. You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension. Footnotes
 | 
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.
Code Review
This pull request adds documentation for two new system variables: tidb_opt_enable_no_decorrelate_in_select and tidb_opt_enable_semi_join_rewrite. The changes are generally good. I've suggested a few minor improvements for clarity and consistency with the style guide. I also pointed out a potential technical inaccuracy in the description of tidb_opt_enable_semi_join_rewrite based on the existing documentation for the corresponding hint.
| @terry1purcell Could you please invite a tech reviewer? Thanks! | 
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
| - Default value: `OFF` | ||
| - This variable controls whether to enable the [Cross-database binding](/sql-plan-management.md#cross-database-binding) feature. | ||
| ### tidb_opt_enable_no_decorrelate_in_select <span class="version-mark">New in v8.5.4</span> | 
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.
| ### tidb_opt_enable_no_decorrelate_in_select <span class="version-mark">New in v8.5.4</span> | |
| ### tidb_opt_enable_no_decorrelate_in_select <span class="version-mark">New in v8.5.4 and v9.0.0</span> | 
| - Default value: `OFF` | ||
| - This variable controls whether to apply the hint [`NO_DECORRELATE`](/optimizer-hints.md#no_decorrelate) at the session/global level for all queries with a subquery in the select list. | ||
| ### tidb_opt_enable_semi_join_rewrite <span class="version-mark">New in v8.5.4</span> | 
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.
| ### tidb_opt_enable_semi_join_rewrite <span class="version-mark">New in v8.5.4</span> | |
| ### tidb_opt_enable_semi_join_rewrite <span class="version-mark">New in v8.5.4 and v9.0.0</span> | 
| - Applies to hint [SET_VAR](/optimizer-hints.md#set_varvar_namevar_value): Yes | ||
| - Type: Boolean | ||
| - Default value: `OFF` | ||
| - This variable controls whether to apply the hint [`NO_DECORRELATE`](/optimizer-hints.md#no_decorrelate) at the session/global level for all queries with a subquery in the select list. | 
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.
| - This variable controls whether to apply the hint [`NO_DECORRELATE`](/optimizer-hints.md#no_decorrelate) at the session/global level for all queries with a subquery in the select list. | |
| - This variable controls whether the optimizer applies the [`NO_DECORRELATE()`](/optimizer-hints.md#no_decorrelate) hint at the session or global level for all queries that contain a subquery in the `SELECT` list. | 
| - Applies to hint [SET_VAR](/optimizer-hints.md#set_varvar_namevar_value): No | ||
| - Type: Boolean | ||
| - Default value: `OFF` | ||
| - This variable controls whether to apply the hint [`SEMI_JOIN_REWRITE`](/optimizer-hints.md#semi_join_rewrite) at the session/global level for all queries that contain subqueries. | 
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.
| - This variable controls whether to apply the hint [`SEMI_JOIN_REWRITE`](/optimizer-hints.md#semi_join_rewrite) at the session/global level for all queries that contain subqueries. | |
| - This variable controls whether the optimizer applies the [`SEMI_JOIN_REWRITE()`](/optimizer-hints.md#semi_join_rewrite) hint at the session or global level for all queries that contain subqueries. | 
| [LGTM Timeline notifier]Timeline: 
 | 
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.
What is the related PR or file link(s)?
pingcap/tidb#63204
pingcap/tidb#63416
Do your changes match any of the following descriptions?