An open API service indexing awesome lists of open source software.

https://github.com/data-integrations/record-splitter-transform

Given a field and a delimiter, this splits the value into multiple records.
https://github.com/data-integrations/record-splitter-transform

cask-marketplace cdap cdap-plugin split

Last synced: 23 days ago
JSON representation

Given a field and a delimiter, this splits the value into multiple records.

Awesome Lists containing this project

README

          

# Record Splitter Transform

[![cm-available](https://cdap-users.herokuapp.com/assets/cm-available.svg)](https://docs.cdap.io/cdap/current/en/integrations/cask-market.html)
![cdap-transform](https://cdap-users.herokuapp.com/assets/cdap-transform.svg)
[![License](https://img.shields.io/badge/License-Apache%202.0-blue.svg)](https://opensource.org/licenses/Apache-2.0)
[![Join CDAP community](https://cdap-users.herokuapp.com/badge.svg?t=wrangler)](https://cdap-users.herokuapp.com?t=1)

The [Record Splitter Transform](docs/RecordSplitter-transform.md) splits a value into multiple records, given a field and a delimiter.

Build
-----
To build your plugins:

mvn clean package -DskipTests

The build will create a .jar and .json file under the ``target`` directory.
These files can be used to deploy your plugins.

UI Integration
--------------
The CDAP Pipeline UI displays each plugin property as a simple textbox. To customize how the plugin properties
are displayed in the UI, you can place a configuration file in the ``widgets`` directory.
The file must be named following a convention of ``[plugin-name]-[plugin-type].json``.

See [Plugin Widget Configuration](http://docs.cdap.io/cdap/current/en/hydrator-manual/developing-plugins/packaging-plugins.html#plugin-widget-json)
for details on the configuration file.

The UI will also display a reference doc for your plugin if you place a file in the ``docs`` directory
that follows the convention of ``[plugin-name]-[plugin-type].md``.

When the build runs, it will scan the ``widgets`` and ``docs`` directories in order to build an appropriately
formatted .json file under the ``target`` directory. This file is deployed along with your .jar file to add your
plugins to CDAP.

Deployment
----------
You can deploy your plugins using the CDAP CLI:

> load artifact config-file

For example, if your artifact is named 'example-plugins-1.0.0':

> load artifact target/example-plugins-1.0.0.jar config-file target/example-plugins-1.0.0.json