feat(docs): add taosx datain Pulsar/Pulsar-Tuya docs

[acerDebugman]

Closes 6496667662

Description

Issue(s)

• Close/close/Fix/fix/Resolve/resolve: Issue Link

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]

Summary of Changes

Hello @acerDebugman, I'm Gemini Code Assist¹! 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 introduces comprehensive documentation for integrating Apache Pulsar and Tuya's customized Pulsar-Tuya platform with TDengine TSDB. The new guides provide step-by-step instructions for users to set up data migration tasks, enabling efficient historical data transfer and real-time data ingestion from these messaging platforms into TDengine TSDB. This enhancement aims to simplify the process of connecting these data sources, improving the overall user experience for data integration.

Highlights

• New Pulsar Integration Documentation: Comprehensive documentation has been added for integrating Apache Pulsar with TDengine TSDB, providing step-by-step instructions for data migration tasks.
• New Pulsar-Tuya Integration Documentation: Dedicated documentation is now available for integrating Pulsar-Tuya, a customized Pulsar cluster by Tuya, with TDengine TSDB, including specific authentication details for the Tuya platform.
• Detailed Configuration Guides: Both Pulsar and Pulsar-Tuya guides cover essential configuration steps such as basic task setup, connection information, various authentication mechanisms (Basic Auth, JWT, mTLS, Custom), data collection settings, payload parsing (JSON, field splitting, filtering), and table mapping.
• Multilingual Support: The new integration guides are provided in both English and Chinese versions to cater to a broader audience.

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

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

[gemini-code-assist]

Code Review

This pull request adds documentation for Pulsar and Pulsar-Tuya data sources in both English and Chinese. While this is a valuable addition, the current implementation has several issues that need to be addressed to ensure quality and consistency.

• Inconsistent Content: There is a significant discrepancy between the English and Chinese documentation. The Chinese documents include detailed sections on "Advanced Options" and "Exception Handling Strategy" by importing shared .mdx files, whereas the English documents only show screenshots for advanced options and completely omit the exception handling section. Please update the English documentation to be as comprehensive as the Chinese versions.
• Copy-Paste Errors: Many sections appear to be copied from the Kafka documentation, resulting in incorrect image paths (e.g., kafka-xx.png) and mismatched image alt texts. These must be corrected to point to the appropriate Pulsar/Tuya assets.
• Typos: A recurring typo ("hello-word" instead of "hello-world") is present in the JSON examples across all new files.
• Documentation Quality (Chinese): The Chinese documents use non-descriptive, timestamp-based alt texts for images and have inconsistent image path formats. The import variable for the exception handling strategy is also misleadingly named Contributing.
• File Naming: The Chinese documentation for Pulsar-Tuya (21-tuya-pulsar.mdx) has a different name structure compared to its English counterpart (21-pulsar-tuya.md), which should be standardized.

Addressing these points will greatly improve the quality and usability of the new documentation.