In this lesson you will
- Learn about CloverETL Designer’s environment
- Create your first transformation graph
- Read a CSV file
- Download CloverETL Designer
- Install using on-screen instructions
CloverETL organizes your assets (transformations, data files, metadata, etc.) into projects stored in workspaces (your “root” displayed in Navigator)
We recommend putting your input data files into “data-in” folder. However, your files can live anywhere you want.
The most common object in a CloverETL project is a ‘graph’. A CloverETL graph contains a collection of components configured to read, transform and write data.
A double-click on a component will display the property editor where you can configure the component’s parameters.
Metadata describes data fields, data types, date formats, etc. You need to assign metadata to edges to describe the data flow.
The Metadata Editor allows you to change data types, rename fields, etc.
Metadata is assigned to edges to tell CloverETL what comes through the edge.
Edges can have different visual styles
Dashed red edges need to have metadata assigned
Solid grey edges have meta data explicitly assigned
Dashed grey edges inherit metadata from either previous or following components (this is called automated metadata propagation)
Trash is a useful development component that you can use to incrementally develop your data flows. Trash discards all incoming records, effectively being a dump bin for whatever you’re testing. (/dev/null if you will)
- Trash bs_icon name=”glyphicon glyphicon-new-window”]
Incremental development using Trash
1 Test Reader
2 Test Filter
3 Test Reformat