Find out what is new in Event Processing version 1.0.x.
Release 1.0.5
Enrichment node: Database
Event Processing release 1.0.5 introduces the Database node under a new section called Enrichment. With the database node, you can retrieve data from an external database (PostgreSQL) and integrate the data with the events within your Event Processing flow. For more information, see the database node and the associated tutorial about enriching events with reference data.
Support for other Kubernetes platforms
In addition to the existing support for the Red Hat OpenShift Container Platform, Event Processing version 1.0.5 introduces support for installing on other Kubernetes platforms that support the Red Hat Universal Base Images (UBI) containers.
Window top-n is now Top-n
In Event Processing release 1.0.5, Window top-n node is renamed to Top-n. For more information, see the top-n node.
Top-n grouping
Event Processing release 1.0.5 introduces top-n grouping. This feature enables you to apply the top-n condition on groups of events that have the same value of one or more properties in each time window. For more information about how to use the Grouped-by field, see Top-n.
New UI section for aggregate and top-n nodes
Event Processing release 1.0.5 introduces a new UI section called Windowed for nodes such as Aggregate and Top-n, which involve time windows. For more information, see Windowed nodes.
Autosave
Event Processing release 1.0.5 introduces autosave to save your flows automatically with user actions. For save status updates, see the canvas header.
- Saving indicates that saving is in progress.
- Saved confirms success.
- Failed indicates that there are errors. If an action fails to save automatically, you receive a notification to try the save again. Click Retry to re-attempt the save. When a valid flow is saved, you can proceed to run the job.
Documentation: Highlighting differences between versions
Any difference in features or behavior introduced by Event Processing 1.0.5 compared to 1.0.4 or earlier is highlighted in this documentation by using the following graphic:
Security and bug fixes
Event Processing release 1.0.5 and IBM Operator for Apache Flink version 1.0.4 contain security and bug fixes.
Release 1.0.4
Additional processor node: Window top-n
Event Processing 1.0.4 introduces a new processor node called Window top-n, which filters out the highest or lowest values of a particular property within a specified time window. For more information, see Window top-n.
Documentation: Highlighting differences between versions
Any difference in features or behavior introduced by Event Processing 1.0.4 compared to 1.0.3 or earlier is highlighted in this documentation by using the following graphic:
Security and bug fixes
Event Processing release 1.0.4 and IBM Operator for Apache Flink version 1.0.3 contain security and bug fixes.
Release 1.0.3
Security and bug fixes
Event Processing release 1.0.3 and IBM Operator for Apache Flink version 1.0.2 contain security and bug fixes.
Release 1.0.2
Flink version updated to 1.17.1
The IBM Operator for Apache Flink version 1.0.1 update includes Apache Flink version 1.17.1.
Updates to Flink samples
In version 1.0.1 and later of the IBM Operator for Apache Flink, the following Flink samples include High Availability updates:
-
Sample Minimal Production is configured with minimal High Availability for the Flink Job Manager. This means that Flink jobs are restarted automatically if the Flink cluster restarts. However, some downtime is expected as there is only a single Job Manager replica. For more information, see Minimal Production.
-
Sample Production - Flink Application Cluster is configured with High Availability for the Flink Job Manager. Thus, a second replica of the Job Manager pod is deployed by this sample, requiring additional CPU and memory. For more information, see resource requirements and Production - Flink Application Cluster.
Security and bug fixes
Event Processing release 1.0.2 contains security and bug fixes.
Release 1.0.1
Security and bug fixes
Event Processing release 1.0.1 contains security and bug fixes.
Release 1.0.0
First General Availability release.