[ISSUE #1097]🚧Support broker receive transaction message-2🔥

[mxsm]

Which Issue(s) This PR Fixes(Closes)

Fixes #1097

Brief Description

How Did You Test This Change?

Summary by CodeRabbit

Release Notes

• New Features

  • Enhanced transaction processing capabilities in the broker.
  • Introduced new asynchronous methods in the BlockingQueue for non-blocking operations.
  • Added new methods for handling operational messages in the TransactionalMessageBridge.

• Bug Fixes

  • Improved error handling and response generation in transaction processing.

• Documentation

  • Updated default values for transaction-related configurations in BrokerConfig.

These updates enhance the functionality, flexibility, and robustness of transaction management within the system.

[coderabbitai]

Caution

Review failed

The pull request is closed.

Walkthrough

The changes in this pull request enhance the transaction processing capabilities of the RocketMQ broker. Key modifications include the introduction of the EndTransactionProcessor, which is now a generic struct capable of handling various transactional message services. The BrokerRequestProcessor has been updated to integrate this new processor, allowing it to manage end transaction requests. Additionally, several related structs and methods have been updated or added to support improved handling of transactional messages, including new asynchronous methods and additional configuration options.

Changes

File Path	Change Summary
rocketmq-broker/src/broker_runtime.rs	Added import for EndTransactionProcessor and updated end_transaction_processor field in BrokerRequestProcessor.
rocketmq-broker/src/processor.rs	Updated end_transaction_processor type signature and added match arm for RequestCode::EndTransaction.
rocketmq-broker/src/processor/end_transaction_processor.rs	Made EndTransactionProcessor generic, added new fields and methods, updated process_request to async.
rocketmq-broker/src/transaction/operation_result.rs	Changed prepare_message field type to Option<MessageExt> and added Default implementation.
rocketmq-broker/src/transaction/queue/default_transactional_message_service.rs	Added new methods and updated existing methods for asynchronous message handling.
rocketmq-broker/src/transaction/queue/message_queue_op_context.rs	Defined MessageQueueOpContext struct with state management features and added multiple methods.
rocketmq-broker/src/transaction/queue/transactional_message_bridge.rs	Added methods for creating operation messages and writing to the message store.
rocketmq-broker/src/transaction/queue/transactional_op_batch_service.rs	Updated struct to include notify, added methods for asynchronous notifications and operations.
rocketmq-broker/src/transaction/transactional_message_service.rs	Updated delete_prepare_message method to async and changed parameter type.
rocketmq-common/src/common/broker/broker_config.rs	Added transaction_timeout and transaction_op_msg_max_size fields to BrokerConfig.
rocketmq/src/blocking_queue.rs	Introduced try_poll and is_empty asynchronous methods to BlockingQueue.

Assessment against linked issues

Objective	Addressed	Explanation
Support broker receive transaction message (Issue #1097)	✅

Possibly related PRs

• [ISSUE #702]🚀Support pull message result handle-2🚀 #706: The changes in this PR involve modifications to the BrokerRuntime struct, which is directly related to the end_transaction_processor field introduced in the main PR, as both deal with transaction processing capabilities.
• [ISSUE #710]🚀Support pull message result handle-3🎨 #721: This PR enhances the TransactionalMessageBridge and its methods, which are relevant to the transaction processing improvements made in the main PR.
• [ISSUE #671]🚀Support pull message consume-4 #675: The modifications in the BrokerRequestProcessor struct and the handling of transaction requests are closely related to the changes made in the main PR regarding transaction processing.
• [ISSUE #658]🚀Support pull message consume #659: The introduction of new handling for message consumption in this PR aligns with the enhancements made in the main PR, particularly in the context of processing transactions.
• [ISSUE #733]🚀Optimize pull message🔥 #734: The optimizations in the consume logic may relate to the transaction processing improvements in the main PR, as both aim to enhance the overall message handling capabilities.

Suggested reviewers

• TeslaRustor

Poem

🐰 In the realm of transactions, we hop with glee,
New processors and methods, oh what a spree!
With messages flowing and queues that align,
Our broker's now ready, it's truly divine!
So let’s celebrate changes, both big and small,
For the world of RocketMQ, we’ll conquer it all! 🌟

---

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Generate unit testing code for this file.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit testing code for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[mxsm]

🚀Thanks for your contribution🎉. CodeRabbit(AI) will review your code first🔥