-
Notifications
You must be signed in to change notification settings - Fork 701
cloud: add Performance and Plus storage #20936
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
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 @qqqdan, 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 size-your-cluster.md
documentation file to include information about the new "Performance and Plus" storage options for TiKV and the "Plus" storage option for TiFlash. It also provides instructions on how to request these features, as they are currently only available upon request for AWS clusters.
Highlights
- TiKV Storage Types: Added documentation for 'Performance and Plus' TiKV storage types, including availability and request instructions.
- TiFlash Storage Types: Added documentation for 'Plus' TiFlash storage type, including availability and request instructions.
Changelog
- tidb-cloud/size-your-cluster.md
- Added 'Performance and Plus storage' to the list of TiKV storage types.
- Added a section describing 'Performance and Plus storage' for TiKV, including details on how to request it.
- Added a section describing 'Plus storage' for TiFlash, including details on how to request it.
- Added 'Plus storage' to the list of TiFlash storage types.
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. ↩
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
The pull request updates the size-your-cluster.md
documentation to include information about the new Performance and Plus storage options for TiKV and TiFlash. The changes are well-structured and provide clear instructions on how to request these features. However, there are a few minor suggestions for improvement.
Summary of Findings
- Inconsistent terminology: The document uses both "Performance and Plus storage" and "Plus storage" for TiKV and TiFlash respectively. It would be better to use consistent terminology across the document to avoid confusion. [^1]
- Missing links: The document mentions "Basic storage" and "Plus storage" for TiFlash, but the corresponding anchor links are missing. [^1]
Merge Readiness
The changes are well-structured and provide clear instructions on how to request the new Performance and Plus storage features. Addressing the minor issues related to terminology consistency and missing links would further improve the document's quality. I am unable to approve the pull request, and recommend that others review and approve this code before merging.
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.
Looks good now
@ginkgoch: adding LGTM is restricted to approvers and reviewers in OWNERS files. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
Co-authored-by: Aolin <[email protected]>
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: Grace Cai <[email protected]>
/unhold |
/approve |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: Oreoxmt The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
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?