CloverETL 4.0

Helping Developers Empower Business

CloverETL 4.0 introduces subgraphs, a powerful way of creating user-defined components that let you hide complexity and design data
transformations on a much higher level, using business components rather than low-level data operations. Also, the new features that support subgraphs are very useful on their own – automatic metadata propagation reduces the need to manage
metadata in transformations, while the execution view panel gives you easier access to debug information for faster development.

Many components now automatically propagate the correct metadata. This minimizes the need to manually select metadata. Subgraphs will also be able to provide you with correct metadata for their outputs or inputs.

When using subgraphs, you can configure them as ordinary components - they have properties with configuration dialogs. Internally, the subgraphs utilize the extended model of graph parameters to define their configuration.

Use Ctrl + mouse click on a Subgraph component to quickly open the subgraph. This action works also for ExecuteGraph, ExecuteJobflow and RunGraph components and allows you to quickly navigate the hierarchy of executed jobs.

Open a currently running or already finished Server job (graph, jobflow) in Designer. Designer will show the graph, tracking information and log updated live, the same as if the job was started from Designer. This can be used to monitor the state of a running job, or for post-mortem analysis of a failed job.

CloverDataReader and CloverDataWriter components were updated to be consistent with other readers and writers (e.g. support partitioned writing, autofilling etc). Additionally, their compression was improved.

Writing into a specific sheet is supported in streaming mode, so the other sheets won't be removed. Please note that the existing sheets must first be loaded into memory, so it's not possible to write huge data into different sheets.

3rd party providers of encryption algorithm for Server configuration can be selected, in a similar way as secure parameters. This allows you to use stronger encryption than provided by default in Java, e.g. BouncyCastle.

If the connection instance is shared by multiple components (i.e. it's not in threadsafe mode) and the components are configured not to perform commit themselves, then a failing graph will not perform commit. This allows you to define a big transaction over the whole graph - if the graph fails, then it will perform rollback.

A new Execution View was introduced that shows the current execution status of a running graph and its sub jobs (e.g. subgraphs). You can access details such as the graph file, log, and tracking information by double clicking on a job.

Selected graph parameters can be marked as public. For subgraphs, these parameters are presented as properties of the parent subgraph component. This allows for easy configuration of a subgraph, making it feel like a component.