*: add analytics service docs#22556
Draft
lilin90 wants to merge 7 commits intopingcap:feature/preview-cloud-lakefrom
Draft
*: add analytics service docs#22556lilin90 wants to merge 7 commits intopingcap:feature/preview-cloud-lakefrom
lilin90 wants to merge 7 commits intopingcap:feature/preview-cloud-lakefrom
Conversation
|
Skipping CI for Draft Pull Request. |
ti-chi-bot
bot
added
the
do-not-merge/work-in-progress
|
[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. DetailsNeeds approval from an approver in each of these files:Approvers can indicate their approval by writing |
ti-chi-bot
bot
added
missing-translation-status
ti-chi-bot
bot
removed
the
missing-translation-status
Contributor
Summary of ChangesHello, 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 significantly expands the documentation for the TiDB Cloud Lake analytics service. It introduces a vast collection of new guides, tutorials, and SQL reference content to provide users with comprehensive resources for understanding and utilizing the platform's capabilities. The additions aim to enhance user experience by offering detailed explanations across various functional areas. Highlights
🧠 New Feature in Public Preview: You can now enable Memory to help Gemini Code Assist learn from your team's feedback. This makes future code reviews more consistent and personalized to your project's style. Click here to enable Memory in your admin console. Changelog
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
|
![gemini-code-assist[bot]](https://avatars.githubusercontent.com/in/956858?s=60&v=4){kind=small}
Contributor
There was a problem hiding this comment.
Code Review
The pull request introduces new documentation for TiDB Cloud Lake, covering various guides, tutorials, and SQL references. The review comments highlight several issues related to inconsistent product naming (replacing "Databend" with "TiDB Cloud Lake"), incorrect relative links, a typo in "atabend", redundant phrasing, and a stray backtick in the Table of Contents. These issues require correction to ensure clarity, consistency, and proper rendering of the documentation.
Standardize and fix internal documentation links and labels for the TiDB Cloud Lake docs. Updated TOC entries to shorter titles, fixed several relative links to point to /tidb-cloud-lake paths (load-from-local-file, load-from-remote-file, and file format references), cleaned up minor whitespace in the input-output-file-formats doc, and added new variables (lake, lake-short) in variables.json.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
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?