|
@@ -4,9 +4,9 @@ Sources feed data into Kuiper from other systems. Kuiper has built-in source sup
|
|
|
|
|
|
## Developing
|
|
|
|
|
|
-### Develop a sink
|
|
|
+### Develop a source
|
|
|
|
|
|
-To develop a sink for Kuiper is to implement [api.Sink](../../../xstream/api/stream.go) interface and export it as a golang plugin.
|
|
|
+To develop a source for Kuiper is to implement [api.Source](../../../xstream/api/stream.go) interface and export it as a golang plugin.
|
|
|
|
|
|
Before starting the development, you must [setup the environment for golang plugin](overview.md#setup-the-plugin-developing-environment).
|
|
|
|
|
@@ -51,6 +51,10 @@ A configuration system is supported for Kuiper extension which will automaticall
|
|
|
1. The name of your configuration file must be the same as the _.so_ file and must be camel case with upper case first letter. For example, MySource.yaml.
|
|
|
2. The yaml file must be located inside _etc/sources_
|
|
|
3. The format of the yaml file could be found [here](../rules/sources/mqtt.md)
|
|
|
+
|
|
|
+#### common configuration field
|
|
|
+
|
|
|
+There is a common configuration field ``concurrency`` to specify how many instances will be started to run the source.
|
|
|
|
|
|
### Package the source
|
|
|
Build the implemented source as a go plugin and make sure the output so file resides in the plugins/sources folder.
|