Skip to content

Conversation

@hjxilinx
Copy link
Contributor

Description

doc: fix SQL example formatting in stream documentation

Issue(s)

https://project.feishu.cn/taosdata_td/job/detail/6761700603

Checklist

Please check the items in the checklist if applicable.

  • Is the user manual updated?
  • Are the test cases passed and automated?
  • Is there no significant decrease in test coverage?

@gemini-code-assist
Copy link
Contributor

Summary of Changes

Hello @hjxilinx, 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 addresses a minor documentation issue by refining a SQL example within the Chinese stream documentation. The change ensures the example for creating a stream is more complete and syntactically correct, thereby enhancing clarity for users.

Highlights

  • Documentation Update: Corrected a SQL example in the Chinese stream documentation by adding the INTO dst_table clause to a CREATE STREAM statement, improving its completeness and accuracy.

🧠 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
  • docs/zh/14-reference/03-taos-sql/14-stream.md
    • Added the INTO dst_table clause to a CREATE STREAM SQL example.
    • Adjusted the formatting of the NOTIFY_HISTORY and ON_FAILURE clauses for better readability.
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 by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

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 pull request 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 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

  1. 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.

Copy link
Contributor

@gemini-code-assist gemini-code-assist bot left a 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 fixes an SQL example in the stream documentation. The changes correctly add the mandatory INTO clause and fix an invalid semicolon placement, making the example syntactically correct. However, there's a remaining issue with a semicolon at the end of the ON_FAILURE PAUSE clause which should be removed to make the entire CREATE STREAM statement valid.

@zitsen zitsen merged commit 0fb8d99 into 3.3.6 Feb 11, 2026
5 checks passed
@zitsen zitsen deleted the hjxilinx-patch-1 branch February 11, 2026 02:55
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants