Manager Custom Plugin

An Inlong Group contains more than one Inlong Stream, each Inlong Stream is capable of a single individual dataflow.
Inlong Group is responsible for physical resource definition shared by all Inlong Streams included, especially middleware clusters and sort functions.
In order to create Inlong Group, Inlong Manager use CreateGroupWorkflowDefinition to init all necessary physical resources, a workflow definition contains several individual service tasks. When it’s created and processed, service tasks will be executed one after another.
Service task is constructed in observer pattern, which also known as the publish-subscribe pattern, each service task will register several task listeners. Listener accepts workflow context and controls execution logic on physical resources.
As a developer, you need to develop specific Listener with personalized logic.

When Inlong Manager is deployed, plugins must be located under installation directory, then Manager Process will find the plugin jar and install the plugin automatically.

As a developer, you can confirm your plugin be loaded successfully by searching logs below:

For helping all Inlong developers. We hava provide manager-plugins in Inlong Manager Module, which provide FlinkSortProcessPlugin as an example; or you can create ProcessPlugin as below;

DataSourceOperateListener,QueueOperateListener,SortOperateListener,SinkOperateListener are child_classes extended from TaskEventListener. Then EventSelector decides whether the listener should be triggered.

After developing you plugin, you should prepare plugin definition file in Yaml, and put it under resources/META-INF.