feat(tmq): [TS-6379]remove limition for table operation in tmq

[wangmm0220]

Description

Please briefly describe the code changes in this pull request.

Jira: https://jira.taosdata.com:18080/browse/TD-

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 @wangmm0220, 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 significantly improves the flexibility of TMQ by lifting restrictions on table operations when topics are active. It achieves this by overhauling the internal schema management and validation mechanisms, ensuring that schema information is directly integrated into the data processing pipeline and consistently provided to consumers. The changes simplify the codebase and enhance the system's adaptability to schema changes.

Highlights

• Removed Restrictions on Table Operations for TMQ Topics: The pull request eliminates previous limitations that prevented certain table operations (such as altering columns or tags) when a TMQ topic was subscribed to that table. This change allows for greater flexibility in schema evolution while using TMQ.
• Simplified Topic Schema Management: The internal mechanism for managing topic-related schema checks has been refactored. This includes removing the STqCheckInfo structure and associated logic, as well as simplifying how AST (Abstract Syntax Tree) and query plan strings are stored and processed for topics.
• Direct Schema Association with Execution Handles: Schema information (SSchemaWrapper) is now directly associated with the execution handle (STqExecCol) for column-based topics. This streamlines schema access and reduces the need for redundant schema extraction or validation steps.
• Consistent Schema Inclusion in Data Responses: The system now consistently includes schema information within SMqDataRsp for all data blocks, ensuring that consumers always receive the necessary schema details alongside the data.
• Streamlined Queue Execution Task Creation: The qCreateQueueExecTaskInfo function has been simplified by removing the numOfCols parameter, as the schema is now directly available through the execution handle.

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 removes limitations on table operations for tables used in TMQ topics, which is a significant feature enhancement. The changes are extensive, involving refactoring of schema handling in TMQ messages and removing restrictive checks in both mnode and vnode. While the overall direction is good, I've identified a critical backward compatibility issue that could impact upgrades, along with two high-severity memory leaks related to schema management in the topic lifecycle. I've provided detailed comments and code suggestions to address these issues. Please review them carefully before merging.