Enh/stream/only createtable supported main

[facetosea]

Description

Please briefly describe the code changes in this pull request.

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 @facetosea, 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 enhances the system's ability to handle stream processing by allowing tables to be created without requiring immediate data insertion. It introduces a new flag to signal this intent, and updates the data handling and insertion logic across the backend to respect this flag. A new test case has been added to ensure the correct behavior of this feature in stream processing scenarios.

Highlights

• New Flag for Table Creation: Introduced a new flag, SUBMIT_REQ_ONLY_CREATE_TABLE, in include/common/tmsg.h to explicitly indicate that a submission request is intended solely for table creation without immediate data insertion.
• Backend Data Handling Logic: Modified source/dnode/vnode/src/vnd/vnodeSvr.c to update vnodeHandleDataWrite and vnodeScanSubmitRowData functions. These functions now check for the SUBMIT_REQ_ONLY_CREATE_TABLE flag and skip data processing if it's set, ensuring that table creation proceeds even with empty data submissions.
• Stream Inserter Behavior: Updated source/libs/executor/src/dataInserter.c to set the SUBMIT_REQ_ONLY_CREATE_TABLE flag within appendInsertData when no valid data is present for insertion. This allows the system to attempt table creation in stream processing contexts even if the initial data block is empty.
• New Test Case for Stream Processing: Added a new test case, Basic13, to test/cases/41-StreamProcessing/05-Notify/test_notify.py. This test specifically validates the scenario where a stream processing operation creates a table without initial data, then inserts data, and verifies the results, ensuring the new flag's functionality is correctly handled.

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 introduces an enhancement to stream processing. When a stream produces no data to insert (for example, due to filtering), it now sends a request with a special flag SUBMIT_REQ_ONLY_CREATE_TABLE instead of failing. This allows the destination table to be created even if the initial data batch is empty. The changes are well-implemented across the data inserter and vnode server logic to handle this new flag correctly. A new test case has been added to verify this behavior. The implementation looks solid and addresses the intended use case effectively.