What's new in Striim Platform 4.2.0

Looking for the Striim Cloud documentation? Click here.

Striim Cloud Mission Critical is now available in Google Cloud and Microsoft Azure. See Introducing Striim Cloud Mission Critical.

The following features are new in Striim Platform 4.2.0.4.

MariaDB Reader, MariaDB Xpand Reader, and MySQL Reader's Connection URL properties support the zeroDateTimeBehavior option.
When using MariaDB Xpand Reader, SkySQL's binlog_format can be default in the global configuration (see MariaDB setup.
Database Writer's Tables property supports the keycolumns() option.
In Azure Databricks, Databricks Writer supports serverless compute (see Learn / Azure Databricks documentation / Serverless compute) and personal staging locations in Azure (see Using an Azure personal staging location).
64-bit Red Hat Enterprise Linux (RHEL) 9.1 and 64-bit Ubuntu 22.04 LTS have been certified as supported operating systems (see System requirements).

The following features are new in Striim Platform 4.2.0.

Web UI

You can set the online help to get the latest documentation from the web rather than the possibly outdated version bundled with the server (see Switching online help links to open the latest docs on the web).
Resource usage policies can help prevent web UI slowdown (see Resource usage policies).
The Apps page has improvements in filtering, sorting, monitoring, and organizing apps.
ROUTER components may be created in the Flow Designer (see CREATE ROUTER).

Wizards support initial schema creation for Salesforce, Salesforce Pardot, and ServiceNow sources.
Schema evolution supports TRUNCATE TABLE for additional sources and targets (see Handling schema evolution).
Schema evolution supports ALTER TABLE ... ADD PRIMARY KEY. and ALTER TABLE ... ADD UNIQUE for MariaDB and MySQL (see Handling schema evolution).

GCS Reader reads from Google Cloud Storage.
Salesforce Pardot Reader reads Salesforce Pardot sObjects.
Salesforce Reader supports JWT Bearer Flow authentication.
BigQuery Writer supports parallel requests when using the Storage Write API and allows specifying HttpTransportOptions timeouts in TQL (see BigQuery Writer properties).
BigQuery Writer supports parallel requests when using the Storage Write API and allows specifying HttpTransportOptions timeouts in TQL (see BigQuery Writer properties).
MongoDB Writer:
- Supports exactly-once processing (see notes for the Checkpoint Collection property).
- Shard key updates have been added to the available Ignorable Exception Code property values.
ServiceNow Writer writes to tables in ServiceNow.

MongoDB Reader:
- Supports MongoDB versions up to 6.3.x.
- In Incremental mode, a single MongoDB Reader can read from an entire cluster using a +srv connection URL.
- With MongoDB 4.2 and later, reads from change streams (see MongoDB Manual > Change Streams) instead of the oplog.
- When reading from change streams, supports transactions and unset operations, and provides additional metadata.
- Can select documents based on queries (see Selecting documents using MongoDB Config).
MSJet supports compressed tables and indexes (see Learn / SQL / SQL Server / Enable Compression on a Table or Index).
Oracle Reader supports Oracle Database 21c.

Resource usage policies can help prevent issues such as running out of memory or disk space to cause applications to halt (see Resource usage policies).
Cluster-level Smart Alerts can be modified in the web UI (see Managing Smart Alerts).
You can set a timeout for web UI and console sessions (see Setting a web UI and console timeout).
Vaults support Google Secrets Manager (see Using vaults).
You can configure access to the following endpoints using Google Private Service Connect (see Using Private Service Connect with Google Cloud adapters:
- BigQuery
- Cloud SQL for MySQL
- Cloud SQL for Postgres
- Google Cloud Storage
- Spanner

You can set the online help to get the latest documentation from the web rather than the possibly outdated version bundled with the server (see Switching online help links to open the latest docs on the web).
You can configure Striim to automatically deactivate a user after a set number of failed login attempts (see Locking out users after failed logins). Deactivated users can be activated again on the Users page of the web UI.