You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Simplify the processing logic of various Listeners - the workflow only needs to be dispatched to the relevant processing Listeners, and the specific execution logic is handed over to the specific executor of this Listener to execute.
For example, to create a Listener of a sink resource, you only need to hold the factory of the implementation class that creates the sink resource. At runtime, the instance is obtained according to the specific type, and the creation process can be implemented by it (such as the Hive library table).
Otherwise, each type of Sink must implement a Listener…
Improve scalability: When other users use this process, they only need to implement the interfaces in the above factories, and they can expand the intranet process without changing the source code of Inlong-Manager.
Describe the proposal
Unify the InlongGroup workflow.
Combining the processes of Lightweight and Standard together, most of the processing logic can be reused.
For processes that need to distinguish between Lightweight and Standard, the configuration of InlongGroup can be used to distinguish them.
[Benefit]
Improve code reusability, thereby reducing maintenance costs.
Simplify the processing logic of various Listeners - the workflow only needs to be dispatched to the relevant processing Listeners, and the specific execution logic is handed over to the specific executor of this Listener to execute.
Improve scalability: When other users use this process, they only need to implement the interfaces in the above factories, and they can expand the intranet process without changing the source code of Inlong-Manager.
Task list
InLong Component
InLong Manager
Are you willing to submit PR?
Code of Conduct
The text was updated successfully, but these errors were encountered: