-
Notifications
You must be signed in to change notification settings - Fork 699
disable switch to import mode for global sort, and add tikv-worker-url config #20866
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
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.
Hello @D3Hunter, 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!
Summary of Changes
This pull request updates the documentation for TiDB. Specifically, it modifies sql-statements/sql-statement-import-into.md
to clarify that switching TiKV to import mode is disabled when using global sort in version v9.0.0-xx and later. It also adds a new configuration option, tikv-worker-url
, to tidb-configuration-file.md
, noting that it's not currently used and might be removed in the future.
Highlights
- Documentation Update: Updated
sql-statements/sql-statement-import-into.md
to reflect the behavior ofDISABLE_TIKV_IMPORT_MODE
when using global sort. - New Configuration Option: Added
tikv-worker-url
totidb-configuration-file.md
with a disclaimer about its current state.
Changelog
- sql-statements/sql-statement-import-into.md
- Clarified that
DISABLE_TIKV_IMPORT_MODE
is automatically enabled for global sort in v9.0.0-xx and later.
- Clarified that
- tidb-configuration-file.md
- Added documentation for the
tikv-worker-url
configuration option. - Included a note that the option is not currently used and may be removed.
- Added documentation for the
Using Gemini Code Assist
The 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 in your pull request via creating an issue comment (i.e. comment on the pull request page) using either /gemini <command>
or @gemini-code-assist <command>
. Below is a summary of the supported commands.
Feature | Command | Description |
---|---|---|
Code Review | /gemini review |
Performs a code review for the current pull request in its current state. |
Pull Request Summary | /gemini summary |
Provides a summary of the current pull request in its current state. |
Comment | @gemini-code-assist | Responds in comments when explicitly tagged, both in issue comments and review comments. |
Help | /gemini help |
Displays a list of available commands. |
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 .gemini/
folder in the base of the repository. Detailed instructions can be found here.
Limitations & Feedback
Gemini Code Assist is currently in preview and 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 to provide feedback.
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
-
Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩
[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 |
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 disables switching to import mode for global sort and adds a tikv-worker-url
configuration option. The changes seem straightforward and address the intended functionality. However, I have a few suggestions regarding documentation clarity and potential future considerations.
Summary of Findings
- Documentation Clarity: The documentation update for
DISABLE_TIKV_IMPORT_MODE
could be more explicit about the conditions under which switching to import mode is disabled. Clarifying the behavior for versions prior to v9.0.0 would improve user understanding. - Unused Configuration Option: The addition of
tikv-worker-url
is noted as not being used in the current version and potentially subject to removal. This could be confusing for users and might warrant a more detailed explanation or a decision to defer its inclusion until it's actively used. - Style Guide Adherence: The documentation changes generally adhere to the style guide, but the comment on line 82 of
tidb-configuration-file.md
could be reworded for better clarity and conciseness, as per the style guide's emphasis on simplicity and readability [^1].
Merge Readiness
The pull request is almost ready for merging. Addressing the documentation clarity and the unused configuration option would improve the overall quality. I am unable to approve this pull request, and recommend that another reviewer does so after the below comments are addressed.
Co-authored-by: gemini-code-assist[bot] <176961590+gemini-code-assist[bot]@users.noreply.github.com>
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)?
Do your changes match any of the following descriptions?