What's new and changed in IBM StreamSets

IBM StreamSets updates can include new features and fixes. Releases are listed in reverse chronological order so that the latest release is at the beginning of the topic.

You can see a list of the new features for the platform and all of the services at What's new in IBM Software Hub.

Installing IBM StreamSets

Ready to install IBM StreamSets?

To install IBM StreamSets along with the other IBM Software Hub services, see Installing IBM Software Hub.
To upgrade IBM StreamSets along with the other IBM Software Hub services, see Upgrading IBM Software Hub.
To install or upgrade IBM StreamSets independently, see IBM StreamSets.

Remember: All of the IBM Software Hub components that are associated with an instance of IBM Software Hub must be installed at the same version.

IBM Software Hub Version 5.1.3

A new version of IBM StreamSets was released in April 2025 with IBM Software Hub 5.1.3.

Operand version: 6.0.3

This release includes the following changes:

New features

This release of IBM StreamSets includes the following features:

Use OpenShift Data Foundation storage: You can now use OpenShift Data Foundation as a persistent storage solution for IBM StreamSets.
Uninstall IBM StreamSets by using the standard service uninstallation method: You can now uninstall IBM StreamSets on IBM Software Hub version 5.1.3 in the same way that you uninstall other services. Previously, IBM StreamSets required a separate uninstallation process.
Automatically scale pods for Kubernetes deployments based on multiple metrics: You can configure a Kubernetes deployment to use full autoscaling in IBM StreamSets. With full autoscaling, the IBM StreamSets Kubernetes agent automatically scales the number of pods that host engine instances based on selected metrics, which can include CPU usage, memory usage, and a running pipeline count.; You can continue to use legacy autoscaling for Kubernetes deployments. However, legacy autoscaling scales the number of pods based on CPU usage only.

Issues fixed in this release

The following issues were fixed in this release:

Accessing the Sequences page can incorrectly redirect to the Welcome page

Issue: When you navigate to the Sequences page and do not have the Job Operator role, you are incorrectly redirected to the Welcome page.
Resolution: You can now access the Sequences page without the Job Operator role.

Copying and pasting a stage in the canvas does not work for most browsers

Issue: You cannot copy and paste a stage in the pipeline canvas when you use Google Chrome, Firefox, or Microsoft Edge.
Resolution: You can now copy and paste a stage in the pipeline canvas on all supported browsers.

IBM StreamSets API incorrectly allows creating a job without pipeline access

Issue: The IBM StreamSets API, including SDK usage, incorrectly allows you to create a job for a pipeline when you do not have read permission on that pipeline.
Resolution: The API now requires that you have read permission on the pipeline, just as the user interface requires.

Editing deployments incorrectly requires the Environment Manager role

Issue: You cannot edit deployments unless you have the Environment Manager role.
Resolution: You can now edit deployments when you have the Deployment Manager role.

New pipeline canvas incorrectly displays connection properties defined with a parameter

Issue: When you use a parameter for a connection property, the new pipeline canvas incorrectly displays the remaining connection properties rather than hiding the properties.
Resolution: When you use a parameter for a connection property, the new pipeline canvas now hides the remaining connection properties, just as the classic pipeline canvas does.

Cannot use a parameter in some stage properties when using the new pipeline canvas

Issue: You cannot use a parameter in stage properties on the Test Origin, Start Event, or End Event tab when using the new pipeline canvas.
Resolution: You can now use a parameter in stage properties on the Test Origin, Start Event, or End Event tab when using the new pipeline canvas.

New pipeline canvas incorrectly displays Use Parameter icon for some properties

Issue: The new pipeline canvas incorrectly displays the Use Parameter icon for properties that display as a field selector and accept multiple values. You cannot use parameters in field selector properties that accept multiple values.
Resolution: The new pipeline canvas no longer displays the Use Parameter icon for properties that display as a field selector.

Jobs can incorrectly save default parameter values

Issue: When you edit a job that uses runtime parameters, the default parameter values are saved with the job as if you had overridden the defaults. As a result, when the job is upgraded to a later pipeline version that uses new default parameter values, the job does not use the updated default values.
Resolution: An edited job no longer saves default parameter values as if you had overridden the defaults.

Customer-reported issues fixed in this release

For a list of customer-reported issues that were fixed in this release, see the Fix List for IBM Cloud Pak® for Data on the IBM Support website.

Security issues fixed in this release

The following security issues were fixed in this release:

CVE-2025-0395, RHSA-2025:1330, RHSA-2025:0324

CVE-2024-57699, CVE-2024-56337, CVE-2024-52046, CVE-2024-50379, CVE-2024-47561, CVE-2024-47175, CVE-2024-45338, CVE-2024-45337, CVE-2024-41110, CVE-2024-37371, CVE-2024-37370, CVE-2024-33599, CVE-2024-29131, CVE-2024-26462, CVE-2024-26461, CVE-2024-22262, CVE-2024-22259, CVE-2024-22243, CVE-2024-12085, CVE-2024-11053, CVE-2024-10963, CVE-2024-10220, CVE-2024-9287, CVE-2024-7254, CVE-2024-6232, CVE-2024-6119, CVE-2024-5535, CVE-2024-4741, CVE-2024-3596, RHSA-2024:10244, RHSA-2024:9333

CVE-2023-50387, CVE-2023-38709

CVE-2019-12900

DSA-5764-1

IBM Software Hub Version 5.1.2

A new version of IBM StreamSets was released in March 2025 with IBM Software Hub 5.1.2.

Operand version: 6.0.0

This release includes the following changes:

New feature

This release of IBM StreamSets includes the following feature:

Upgrade IBM StreamSets by using the standard service upgrade method: You can now upgrade IBM StreamSets on IBM Software Hub version 5.1.1 in the same way that you upgrade any other service. Previously, IBM StreamSets required a separate upgrade process.

Issues fixed in this release

This release of the service includes various fixes.

Customer-reported issues fixed in this release

For a list of customer-reported issues that were fixed in this release, see the Fix List for IBM Cloud Pak for Data on the IBM Support website.

Security issues fixed in this release

The following security issues were fixed in this release:

CVE-2025-26519, CVE-2025-0725, CVE-2025-0665, RHSA-2025:1517

CVE-2024-38821, CVE-2024-36114

CVE-2023-44487, CVE-2023-34062, CVE-2023-34054, CVE-2023-34034

GHSA-xpw8-rcwv-8f8p

IBM Software Hub Version 5.1.1

A new version of IBM StreamSets was released in February 2025 with IBM Software Hub 5.1.1.

Operand version: 6.0.0

This release includes the following changes:

New features

This release of IBM StreamSets includes the following features:

Install IBM StreamSets by using the standard service installation method

You can now install IBM StreamSets on IBM Software Hub in the same way that you install any other service. Previously, IBM StreamSets required a separate installation process.

Deploy Data Collector version 6.1.0

You can now deploy a Data Collector engine version 6.1.0. With version 6.1.0, you can:

Use a reusable connection for a Splunk destination rather than directly entering the details in the destination.
Specify a single Kafka stage library for all supported Kafka versions when you configure any Kafka stage.

For a full list of the new features, see 6.1.x Release Notes in the IBM StreamSets documentation.

Create an engineless connection for easy access to the latest stage libraries

In addition to standard connections, which are based on a selected authoring Data Collector, you can now create engineless connections. An engineless connection can use any stage library that is associated with the latest Data Collector version.

Updates

The following updates were introduced in this release:

When a Kubernetes deployment remains in an Activating or Deactivating state indefinitely, you can now force the deployment to stop and then manually delete any abandoned resources in the Kubernetes cluster.
For sequences, the step where you configure the step start condition has changed. You now configure the condition on the step that starts after an error, not on the step that encounters the error.

Issues fixed in this release

The following issues were fixed in this release:

You cannot delete the current pipeline version when a draft run exists

Issue: You cannot delete the current version of a pipeline if a draft run exists for that version.
Resolution: You can now delete the current version of a pipeline when a draft run exists for that version.

Preview output displays no value for fields with value of 0

Issue: When you preview a pipeline that includes a field with a time value of 0, the preview output displays no value for the field.
Resolution: Preview output now correctly displays 0 for a field with a time value of 0.

Creating or editing connections incorrectly requires the Deployment Manager role

Issue: You cannot create or edit connections unless you have the Deployment Manager role.
Resolution: You can now create or edit connections when you have the Connection Editor and the Engine Creator or Administrator roles.

You cannot upgrade multiple jobs at the same time

Issue: When you select multiple jobs in the Job Instances view, and then click More > Use Latest Pipeline Version, the Upgrade Jobs dialog box lists only one job.
Resolution: The Upgrade Jobs dialog box now lists all selected jobs so that you can upgrade multiple jobs at the same time.

Global search does not correctly display a newly selected job

Issue: When you switch between jobs with the global search in the toolbar, the job configuration continues to display property values for the previously viewed job.
Resolution: Switching between jobs with global search now correctly displays property values for the newly selected job.

Offsets not maintained when previous job run had no available engine

Issue: Offsets are not maintained when the previous job run had no available engine.
Resolution: Control Hub now correctly maintains offsets when the previous job run had no available engine.

The Add Stage icon might fail to insert a fragment when more than 50 published fragments exist

Issue: When you have more than 50 published fragments and you use the Add Stage icon from an open lane to insert a fragment, Control Hub fails to insert the selected fragment if it is one of the most recently published fragments.
Resolution: You can now use the Add Stage icon to insert any fragment.

Editing a Kubernetes deployment fails to restart engines

Issue: When you edit an active Kubernetes deployment and then immediately click restart Engines, the engines fail to restart because the deployment is in the Activating state.
Resolution: Control Hub now waits a few minutes for the edited deployment to transition to an Active state, and then restarts the engines.

For a full list of the issues fixed in Data Collector 6.1.0, see 6.1.x Release Notes in the IBM StreamSets documentation.

Customer-reported issues fixed in this release

For a list of customer-reported issues that were fixed in this release, see the Fix List for IBM Cloud Pak for Data on the IBM Support website.

Security issues fixed in this release

The following security issues were fixed in this release:

CVE-2024-52046, CVE-2024-50379, CVE-2024-47535, CVE-2024-38821, CVE-2024-38809

PRISMA-2023-0067

CVE-2020-13936

IBM Software Hub Version 5.1.0

A new version of IBM StreamSets was released in December 2024 with IBM Software Hub 5.1.0.

Operand version: 5.1.0

IBM StreamSets is a new service available with IBM Software Hub 5.1.0.

With the IBM StreamSets service, you can build streaming data pipelines to act on time-sensitive data and enhance real-time decision making.

Data engineers use IBM StreamSets to build, run, and monitor streaming data pipelines that access and connect data across various types of data sources.

With IBM StreamSets data engineers can:

Collaboratively build pipelines.
Access multiple types of external systems.
Detect and correct unexpected data drift.