Enhance the processing capacity of Linkis RPC, and maintain the backward compatibility with Linkis0.x RPC #614
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What is the purpose of the change
closed #569
Add the Linkis Message-Scheduler module to enhance the processing capacity of Linkis RPC.
Brief change log
Support synchronously and asynchronously processing message, and the receiver is identified through annotations.
When processing messages, support sending messages to other receivers in the meanwhile. For example, after EngineConn is started, AM needs to notify Label to register the label information of EC.
Messages are able to be processed by multiple receivers at the same time. For example, ECM registration request needs to register basic information in AM and register resource information in RM.
Support multiple receivers to execute in a single chain sequence, and multually transfer intermediate variables. For example, when EngineConn exits, you need to complete RM information logout, label information logout and AM instance information processing in order.
Support multiple receivers to execute in the order of multiple chains.
Support skipping receivers, for example, after a receiver has been completed and satisfied the conditions, you can skip the subsequent message receivers.
Support integrating RestFul with Message-scheduler, and thus reducing the development of the repeated logic between RPC and RestFul.