CloverETL 4.7.0 (Milestone 1)

This is a milestone preview release. For latest production release please refer to CloverETL 4.6 Release Notes.

CloverETL 4.7 Milestone 1 brings a major new feature—Data Services.

With Data Services you can publish a transformation graph as a REST API endpoint. That means you can create smart data sources or data targets that process data on the fly and make either data, or business logic or a combination of both, available to applications on-demand.


About this release: This is a milestone release that we publish as a preview of the upcoming CloverETL 4.7 version. You can expect the production-ready release in September 2017.

Milestone versions are not recommended as a production upgrade. However, some clients successfully run applications using the milestone releases without trouble.


Released July 19, 2017
  • Milestone
Recent Releases
4.7.0-M1 July 19, 2017
4.6.1 July 19, 2017
4.6.0 June 13, 2017
4.5.0 Mar 14, 2017
4.4.1 Feb 14, 2016
4.3.1 Nov 10, 2016
4.2.1 Aug 18, 2016
4.1.4 Jun 1, 2016

See all releases


New features in 4.7 Milestone 1


Data Services—Publish data and transformations as REST API

CloverETL - Data Services

We're introducing a new Data Service REST job, a data transformation just like regular transformation graph, that can be published on CloverETL Server as a REST API endpoint.

While transformations are traditionally executed by a scheduler or event trigger, Data Services jobs introduce a completely new way of interacting with CloverETL Server and architecting data pipelines across applications using APIs.


Compatibility note—Launch Services: Data Services feature is planned to replace Launch Services in the long-term. However, Data Services are not (currently) compatible with Launch Services—we're building Data Services from the ground up. Launch Services remain fully supported in version 4.7. However, we recommend affected users to become aware of Data Services and their capabilities. There's no rush now, we will announce the replacement plans in more details well ahead, giving current Launch Services users plenty of time to plan and implement the switch.

Contact Us—If you're interested in learning more about Data Services and how it can support your current or planned use of Launch Services/REST API, please contact us through our dedicated Data Services contact form. Our engineers will be able to answer your questions and will be more than happy to show you the new feature and its potential.

CloverETL - Data Services REST job

Installation/Upgrade Instructions for CloverETL 4.7 (Milestone)

To help you install or upgrade to this version, we've prepared a simple checklist:

Before You Upgrade

  • This is a milestone release. We recommend you install this version on a test Server first and use it as a preview of upcoming features and for development. Milestone releases are not supported for production use.

  • Be sure to check the "Compatibility" notes for ALL intermediary releases. We mark all changes that can potentially alter the function of your existing transformations with a "Compatibility" label to make it easier for you. You can safely ignore most of them, as we try hard to keep as much backwards compatibility as we can. There's a comprehensive list of all releases that will help you get the information quickly.
  • Upgrade Designer and Server together. We always release Designer and Server together under a single version. It's highly recommended to upgrade Server and Designer at the same time. Although using different versions of Designer to connect to Server might work, it is not generally supported.
  • There are no incremental patches. We don't release incremental patches. Every upgrade is in fact a full installation that, if installed over older version, will automatically update whatever is necessary in your workspaces, sandboxes, and Server databases as needed.
  • Don't forget to backup. Although none of the above upgrade steps requires explicit backup, we recommend you always back up your work. The upgrade will keep all your transformations, jobflows, and configurations safe. However, as a good word of advice, it never hurts to have a backup.

Designer Upgrade

  • Download the latest version by logging into your customer account. If you no longer have access there, click here to recover your password or contact our CloverCARE Support.
  • Install the new version of Designer. You can install Designer over your existing installation. The process will automatically clean up the old version. Don't worry, you will NOT lose your workspaces, graphs, and transformations. However, if you installed some additional plugins to Designer (Eclipse plugins) you might need to reinstall them. Eclipse should automatically help you do that. When you start the application, point it to your existing workspace directory. With some major releases, we may notify you about upgrading the workspace to the latest version. In such cases, you won't be able to use the workspace with previous versions. Thus, be sure to upgrade all Designers if you're sharing the workspace.
  • Activate the product on first start. You will need a new key as we issue new license keys for every new major version (i.e. from 4.2 to 4.3). However, if you're on our maintenance program, we automatically renew the keys for you. Just go to the download area again and copy/paste the license keys from there. If you can't find the latest keys, please contact us to renew your product maintenance.

Server Upgrade

  • Download the latest version by logging into your customer account. You'll find Server in the same list as Designer downloads. If you no longer have access there, click here to recover your password or contact our CloverCARE Support.
  • Plan for downtime. Upgrading Server requires downtime, so plan your upgrades in advance. If you're running multiple environments, upgrade the non-production installation first and run all your checks there first.
  • Follow step-by-step Server Upgrade Guide. We've prepared detailed instructions on how to properly shut down Server and install a new one. Server will upgrade its database and sandboxes from any previous version automatically.
  • Activate the product on the login screen of Server Console. The license key changes with every major version (i.e. from 4.2 to 4.3) and we automatically renew the keys for you. Just go to the download area again and copy/paste the license key from there.




Detailed list of improvements and fixes in 4.7 (Milestone 1)

Data Services

Major new feature. With Data Services you can combine data and transformations into "smart data endpoints" that you can publish on CloverETL Server as REST API endpoints. This way you can expose a piece of shared data logic implemented as a CloverETL graph or give applications an on-demand access to data that's transformed on-the-fly to meet their requirements.
Major New Feature 4.7.0-M1

Designer Improvements

Graphs are now validated immediately after making changes to component attributes, not just after saving them.
Improvement CLO-10784 4.7.0-M1

Known Issues

Data Services: You currently can't use SpreadsheetDataWriter to output Excel XLSX data as a response:body directly. Currently the only workaround is to create a temporary .xlsx file and then pass the file to the output of the REST job separately.
Known Issue CLO-11240 4.7.0-M1
Data Services job executed from Designer on Cluster will fail if it's executed on a different node. To test a REST job on Cluster during development, we recommend you temporarily publish the job and then simply call the endpoint.
Known Issue CLO-11247 4.7.0-M1
Data Services job configured with POST method fails when explicitly calling getRequestBody() CTL function inside the job (e.g. in Mapping of GetJobInput component). This problem only appears when when data is POSTed from a web form that causes the receiving Data Service job to parse the POST body as parameters, making the body no longer available. In this case, use getRequestParameters() function instead.
Known Issue CLO-11309 4.7.0-M1

Compatibility

Data Services feature is planned to replace Launch Services in the long-term. However, Data Services are not compatible with Launch Service. We're building Data Services from the ground up. Launch Services remain fully supported in version 4.7. However, we recommend affected users to become aware of Data Services and their capabilities. There's no rush now, we will announce the replacement plans in more details well ahead, giving current Launch Services users plenty of time to plan and implement the switch. If you're interested in learning more about Data Services and how it can support your current or planned use of Launch Services/REST API, please contact us through our dedicated Data Services contact form. Our engineers will be able to answer your questions and will be more than happy to show you the new feature and its potential.we will announce the replacement plans in more details well ahead, giving current Launch Services users plenty of time to plan and implement the switch. If you're interested in learning more about Data Services and how it can support your current use of Launch Services, feel free to contact us via our dedicated Data Services contact form, our engineers will contact you shortly.
4.7.0-M1


ETL Developers (This item is most useful for developers; it either brings new functionality for transforming data or brings optimizations)

Administrators (This item is an improvement or feature that will help setup, install, administer and manage the application)

Support (This item helps staff supporting the production operation to identify potential problems or avoid such)