The main star of this release is subgraphs. The addition of subgraphs in CloverETL 4.0 represents one of the biggest conceptual changes we have ever made to CloverETL. But that’s not all. There are many more improvements in CloverETL 4.0 that will make your life easier and give you even more possibilities to work with your data. We hope that you find them as wonderful as we do.
Lets take a look now at the four major improvements in CloverETL 4.0
To explain subgraphs, let’s use an analogy with Legos. Imagine that you bought a Lego set with a selection of standard pieces, but with the ability to create your own blocks. And not only basic shapes – you can create blocks with any kind of functionality. Need an engine for your car model? You can go ahead and create it yourself. And when you are done, it will be the same size as a basic block.
This is very similar to what you can do with subgraphs in CloverETL 4.0. Rather then building complex logic from basic components every time, you only need to create it once, and then you can use it or share with others.
A subgraph can contain a sophisticated function while looking like a simple component.
In the past, working with metadata was not easy as it required a lot of attention to manually manage metadata. You had to keep your eye on your data flows to make sure that you were using the correct metadata. The automated metadata propagation feature in CloverETL 4.0 now significantly reduces this burden. It makes the process much easier: metadata are assigned to an edge and then automatically propagated throughout the graph, depending on the inputs and outputs expected by different components.
Automatic metadata propagation will make work with graphs significantly faster and smoother, shortening the time it takes to create a graph.
We’ve implemented a new and improved runtime for CloverETL 4.0. This allowed us to create a new debugging tool called the Execution View. The Execution View allows you to inspect the whole hierarchy of your jobs at the same time. You can do this both during and after the execution of your graphs. If something goes wrong, you can inspect the job by simply clicking on the error in the Execution View. This will open the job graph editor and highlight the component that caused the error.
The Execution View will be appreciated by developers working on complex graphs, as well as by support teams inspecting jobs in production, as it substantially simplifies finding and debugging errors.
As we are always striving to give users better control over CloverETL, we also introduced several changes in the user interface that will make your life easier. One of them is the detection of unused graph elements. Unused elements are visualized in the Outline view, so you are able to quickly identify and remove them. Another improvement is an updated edge algorithm that produces less intersections between edges, which will make your graphs easier to navigate and to understand. Also, CloverETL now monitors manual changes in your metadata and notifies you with a small tip that hovers over an edge where metadata was recently changed.
CloverETL 4.0 represents a major technological leap forward in the development of CloverETL. With the use of subgraphs, automatic metadata propagation, and all of the other new features for cooperation and teamwork, this version will change the way you work with your data, making it faster, easier, and more efficient than ever before. With the new version of CloverETL, you can work with data within minutes of deploying CloverETL.
