Skip to content

Latest commit

 

History

History
44 lines (29 loc) · 2.06 KB

plugin_development.md

File metadata and controls

44 lines (29 loc) · 2.06 KB
Raw

Plugin Development

Data Prepper supports plugins. All sources, buffers, and processors are created as Data Prepper plugins.

Plugin Requirements

Plugins are created as Java classes. They must conform to the following.

  • The class must be annotated with @DataPrepperPlugin
  • The class must be in the org.opensearch.dataprepper.plugins package
  • The class must implement the required interface
  • The class must have a valid constructor (see below)

Plugin Constructors

The preferred way to create a plugin constructor is to choose a single constructor and annotate it with @DataPrepperConstructor. The constructor can only take in class types which are supported by the plugin framework.

The plugin framework can inject the following types into this constructor:

  • An instance of the plugin configuration class type as defined by DataPrepperPlugin::pluginConfigurationType. The plugin framework will deserialize this type from the Pipeline configuration and supply it in the constructor if requested.
  • An instance of PluginMetrics.
  • An instance of PluginSetting.

If your plugin requires no arguments, it can use a default constructor which will be chosen instead.

Additionally, the plugin framework can create a plugin using a single parameter constructor with a single parameter of type PluginSetting. This behavior is deprecated and planned for removal.

Deploying Maven Artifacts

If you are developing a plugin in another Gradle project your project will depend on at least the data-prepper-api project. You can deploy this artifact locally so that you can add it as a dependency in your other project.

Run the following command:

./gradlew publishToMavenLocal

The Maven artifacts will then be available in your local Maven repository. In standard environments they will be available at ${USER}/.m2/repository/org/opensearch/dataprepper/.