CloverETL 4.5.0 (Milestone 1)

This milestone version is no longer available.
For the production release, please go to CloverETL 4.5 Release Notes.


CloverETL 4.5 Milestone 1 previews another addition to the Salesforce connector family—the Salesforce Wave Writer—and brings further improvements to Server Listeners and introduces simplified controls for restarting jobs.



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

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

Released Jan 31, 2017
  • Milestone
Recent Releases
4.8.0 Dec 13, 2017
4.7.1 Nov 28, 2017
4.7.0 Oct 10, 2017
4.6.1 July 19, 2017
4.5.0 Mar 14, 2017
4.4.1 Feb 14, 2016
4.3.1 Nov 10, 2016

See all releases

Try it yourself

TRY NOW


New features in 4.5 (Milestone 1)


Salesforce Wave Connector

We're introducing new Salesforce Wave writer—a simple solution for loading data into Wave Analytics/BI platform. You can create new datasets and append or update/insert data into existing ones.

CloverETL - Salesforce Wave Writer Connector

Restart jobs on Server

In the Executions History view in Server Console, you can now easily restart jobs using the same parameters as the original execution.

Imagine a file listener starting a job. It passes a file path to the job as a parameter. Restarting such a job requires knowing the exact parameters that the listener provided. With this update, you can easily reuse the starting parameters or even modify them before restarting.


Installation/Upgrade Instructions for CloverETL 4.5

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

Before You Upgrade

  • 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.5 (Milestone 1)

Salesforce CRM Connector

Salesforce Wave writer
New Feature CLO-9493 4.5.0-M1
Support for writing datasets into the Salesforce Wave analytics platform. Supports creating new data sets, as well as append, upsert and delete

MongoDB Support

Authentication Database can now be specified as part of a MongoDB connection.
New Feature CLO-5728 4.5.0-M1
See more details https://docs.mongodb.com/manual/core/security-users/#user-authentication-database
"Use SSL" new configuration option available on MongoDB connection
New Feature CLO-9579 4.5.0-M1
Bundled driver updated to version 3.4. Older versions are still supported.
Improvement CLO-10175 4.5.0-M1

File Event Listeners

Show 10 last performed file listener checks and their status
Improvement CLO-10025 4.5.0-M1
File listeners can now be set to ignore zero-length files
New Feature CLO-9845 4.5.0-M1

UI Improvements

"Enable with condition" dialog now allows creating new parameters directly.
Improvement CLO-9957 4.5.0-M1
This makes it easier to set up, withour prior definition of the required parameter
JSON and XML Extract mapping dialogs now validate metadata, no longer allowing you to create invalid metadata by accident.
Improvement CLO-7448 4.5.0-M1
Added consistency check on readers: Error edge only makes sense if Data policy is set to Controlled
Improvement CLO-9927 4.5.0-M1

Server

Restart job with same parameters
New Feature CLO-9499 CLO-9709 4.5.0-M1
Now you can restart a job with the same input parameters (or you can change them before running the job). This greatly simplifies restarting jobs with parameters provided by Listeners or other parameter-driven automation.

Other Improvements

Fixed confusing error message on UniversalDataReader when maximum number of errors was exceeded
Improvement CLO-10084 4.5.0-M1
Cluster: Auto resume counter is reset after 4 hours of continuous success checks
Improvement CLO-10071 4.5.0-M1
Performance improved for Titan FTP Server
Improvement CLO-8609 4.5.0-M1

Fixes

Fixed MSSQLDataWriter with sqlncli (bcp for linux) throwing "Unable to open BCP host data-file"
Fix CLO-9873 4.5.0-M1

Compatibility

JSch library updated to 0.1.54 (S/FTP)
Compatibility CLO-6538 4.5.0-M1
MongoDB: Bundled driver updated to version 3.4. Older versions are still supported.
Compatibility CLO-10175 4.5.0-M1

Known Issues



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)