feat: add FORCE option for compact command

[hzcheng]

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 @hzcheng, 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 a new FORCE option for the COMPACT SQL command, enhancing data maintenance capabilities by allowing administrators to explicitly trigger compaction processes regardless of recent data writes. This ensures greater control over storage optimization, particularly in scenarios where data might be static but compaction is still desired for other reasons. The implementation involves updates across the system's parsing, internal data handling, and documentation layers to fully support this new functionality.

Highlights

• New FORCE Option for COMPACT Command: The COMPACT SQL command now supports a FORCE option, allowing users to explicitly trigger compaction for databases or vgroups.
• Forced Compaction Behavior: This new option enables compaction of file groups even if no new data has been written since the last compaction, providing greater control over data maintenance.
• Documentation Updates: The English and Chinese operation manuals have been updated to include the new FORCE keyword in the COMPACT command syntax and explain its functionality.
• Internal System Integration: The force flag has been integrated into various internal data structures (e.g., SCompactDbReq, SCompactVnodeReq, SCompactDatabaseStmt, SCompactVgroupsStmt, SCompactArg), serialization/deserialization logic, and the SQL parser to ensure end-to-end support for the new option.

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 a FORCE option for the COMPACT command, allowing compaction to run even if no new data has been written. The changes are implemented consistently across the stack, from the SQL parser to the underlying storage message formats. The code modifications are correct and handle backward compatibility for message formats properly. I have one suggestion to improve the wording in the English documentation for better clarity.

[gemini-code-assist]

The wording of this sentence could be improved for clarity. Consider rephrasing to make it more natural for English readers.

Suggested change

	- The file group will not compact if no new data is written since the last compact unless the FORCE keyword is specified
	- A file group will not be compacted if no new data has been written since the last compaction, unless the FORCE keyword is specified