Sink Extension

Sink feed data from eKuiper into external systems. eKuiper has built-in sink support for MQTT broker and log sink. There are still needs to publish data to various external systems include messaging systems and database etc. Sink extension is presented to meet this requirement.

Developing

Develop a sink

To develop a sink for eKuiper is to implement api.Sink interface and export it as a golang plugin.

Before starting the development, you must setup the environment for golang plugin.

To develop a sink, the Configure method must be implemented. This method will be called once the sink is initialized. In this method, a map that contains the configuration in the rule actions definition is passed in. Typically, there will be information such as host, port, user and password of the external system. You can use this map to initialize this sink.

//Called during initialization. Configure the sink with the properties from action definition 
Configure(props map[string]interface{}) error

The next task is to implement open method. The implementation should be synchronized to create a connection to the external system. A context parameter is provided to retrieve the context information, logger and rule meta information.

//Should be sync function for normal case. The container will run it in go func
Open(ctx StreamContext) error

The main task for a Sink is to implement collect method. The function will be invoked when eKuiper feed any data into the sink. As an infinite stream, this function will be invoked continuously. The task of this function is to publish data to the external system. The first parameter is the context, and the second parameter is the data received from eKuiper. The data could be 2 types:

1. Map slice []map[string]interface{}: this is the default data type.
2. Map map[string]interface{}: this is a possible data type when the sendSingle property is set.

Most of the time, the map content will be the selective fields. But if sendError property is enabled and there are errors happen in the rule, the map content will be like {"error":"error message here"}.

The developer can fetch the transformed result from the context method ctx.TransformOutput(data). The return values are the transformed value of []byte type. Currently, it will be transformed to the json byte array be default or formatted with the set dataTemlate property. If the value is transformed by dataTemplate, the second return value will be true.

The developer can return any errors. However, to leverage the retry feature of eKuiper, the developer must return an error whose message starts with “io error”.

//Called when each row of data has transferred to this sink
Collect(ctx StreamContext, data interface{}) error

The last method to implement is Close which literally close the connection. It is called when the stream is about to terminate. You could also do any clean up work in this function.

Close(ctx StreamContext) error

As the sink itself is a plugin, it must be in the main package. Given the sink struct name is mySink. At last of the file, the sink must be exported as a symbol as below. There are 2 types of exported symbol supported. For sink extension, states are usually needed, so it is recommended to export a constructor function.

func MySink() api.Sink {
    return &mySink{}
}

The Memory Sink is a good example.

Parse dynamic properties

For customized sink plugins, users may still want to support dynamic properties like the built-in ones.

In the context object, a function ParseTemplate is provided to support the parsing of the dynamic property with the go template syntax. In the customized sink, developers can specify some properties to be dynamic according to the business logic. And in the plugin code, use this function to parse the user input in the collect function or elsewhere.

// Parse the prop of go template syntax against the current data.
value, err := ctx.ParseTemplate(s.prop, data)
// Use the parsed value for the following business logic.

Package the sink

Build the implemented sink as a go plugin and make sure the output so file resides in the plugins/sinks folder.

go build -trimpath -modfile extensions.mod --buildmode=plugin -o extensions/sinks/MySink.so extensions/sinks/my_sink.go

Usage

The customized sink is specified in a actions definition. Its name is used as the key of the action. The configuration is the value.

If you have developed a sink implementation MySink, you should have:

1. In the plugin file, symbol MySink is exported.
2. The compiled MySink.so file is located inside plugins/sinks

To use it, define the action mySink inside a rule definition:

{
  "id": "rule1",
  "sql": "SELECT demo.temperature, demo1.temp FROM demo left join demo1 on demo.timestamp = demo1.timestamp where demo.temperature > demo1.temp GROUP BY demo.temperature, HOPPINGWINDOW(ss, 20, 10)",
  "actions": [
    {
      "mySink": {
        "server": "tcp://47.52.67.87:1883",
        "topic": "demoSink"
      }
    }
  ]
}

Whereas, mySink is a key of the actions. The value of mySink is the properties for that sink.