Skip to main content

Release notes

The following are the release notes for Striim Platform 5.4.2.

Requirements

RHEL versions 7.9 and 9.4 and Ubuntu version 18.04 LTS that were certified for Striim 5.2.0 are not certified for 5.4.x. We strongly recommend that before upgrading to 5.4.2 you upgrade to a certified operating system (see System requirements).System requirements

Changes that may require modification of your TQL code, workflow, or environment

  • Striim Platform ships with Kafka 3.9.1. The following High CVEs (see www.cve.org) have been observed in this version of Kafka:

    • CVE-2026-35554

    • CVE-2026-44249

    • CVE-2026-45416

    • CVE-2026-50010

    To mitigate these, Striim recommends downloading and running Kafka 4.x (see Using an external Kafka server).

  • Starting with release 5.4.2, Salesforce CDC Reader changes the metadata and the values that it generates, as follows:

    • Salesforce system fields, such as LastModifiedDate and OwnerId, are detected by default. Audit, derived, and formula fields are not detected.

    • Compound fields are flattened by default.

    • Compound field values are returned in JSON format rather than as strings.

    • When schema evolution is enabled, compound fields are propagated together with their child fields.

    As a result of these changes, the Striim type in an existing application may no longer match the data array that the reader generates. Applications with schema evolution enabled are expected to terminate after you upgrade to 5.4.2.

    To resume processing, note the Replay ID of the last successfully processed event, then recreate the application and configure it to start from that Replay ID:

    1. In the Striim console, run the following command, where <source component name> is the name of the Salesforce CDC Reader source:

      MON <source component name>;
    2. In the output, find Last Event Position. It is similar to the following:

      {ObjectName=SalesforceCdcSourcePosition [replayFromID=*****, schemaId=*****]}

      Note the value of replayFromID. This is the Replay ID.

    3. Create the new application. In Advanced Settings, set Start Position to Replay ID and enter the Replay ID you noted.

    4. Start the application. Processing continues from the last successfully processed event.

  • Starting with release 5.4.2, Salesforce CDC Reader does not support undeleted columns. Salesforce can restore a deleted custom field along with its data, but Striim does not replicate that restoration. When CDDL is enabled, dropping a column at the source hard-deletes the corresponding column at the target.

    When a custom field is deleted, Salesforce appends a _del suffix to its API name, and columns with this suffix are excluded from the Striim data pipeline. Salesforce advises removing the suffix when you undelete the field. Doing so can return the column to the pipeline, but the values that were in the deleted column are not restored.

  • Starting with release 5.4.2, you can use the Striim wizard to create an application that combines Salesforce Reader and Salesforce CDC Reader to perform an initial load followed by continuous replication. Salesforce Reader performs the initial load using a SELECT query, and Salesforce CDC Reader performs ongoing replication by reading change events. Because the two readers retrieve data through different mechanisms, the set of columns emitted during the initial load may differ from the set emitted during CDC; use ColumnMap() at the target to align the two schemas.

  • Starting with release 5.4.2, the default value of ServiceNow Reader's Fetch Size property has been reduced from 10000 to 1000. Applications created in earlier releases retain their existing Fetch Size value.

  • Starting with release 5.4.2, for Salesforce Reader, Salesforce CDC Reader, Salesforce Writer, and Salesforce Pardot Reader, the Consumer Secret property is no longer used and no longer appears in the Flow Designer when OAuth Authorization Flows is JWT_BEARER.

  • Starting with release 5.4.0.2, the Oracle Reader property Read Archive Logs Only has been renamed Archive Fence.

  • Kafka Reader and Kafka Writer versions 0.11 and 2.1.1 are no longer supported. As part of upgrading to Striim 5.4, all Kafka Reader and Kafka Writer adapters in created or quiesced applications will be upgraded to the new versions of the adapters and corresponding connection profiles will be created. If after upgrading you need to import TQL exported from Striim 5.2 or earlier, edit the TQL before importing to use the new properties, and create a connection profile with the appropriate properties. For more information, see Upgrading from Kafka Reader 2.1 or Upgrading Existing Applications that use Kafka Writer.

  • Starting with release 5.4.0.2, the connection profile endpoint type BigQuery Metastore Catalog has been renamed BigLake Metastore Catalog, to reflect the name change by Google. On upgrading, BigQuery Metastore Catalog connection profiles will automatically be converted to BigLake Metastore Catalog connection profiles.

  • Starting with release 5.2.0, the syntax for defining external sources using the CREATE EXTERNAL SOURCE statement has been updated to simplify configuration and support additional source types. For details and updated examples, see CREATE EXTERNAL SOURCE.CREATE EXTERNAL SOURCE

  • The event AIData data model for Sentinel was modified in 5.0.6, with the names of two fields updated from 5.0.2. The number of unique sensitive data identifiers is now specified by numIdentifiers (formerly, Identifiers in 5.0.2), and the number of occurrences of all sensitive data identifiers is now specified by numOccurrences (formerly, Occurrences in 5.0.2).

  • Starting with release 5.4.0.2, Striim Platform requires JDK 17. Due to this change, once you upgrade to Striim 5.4.0.2, it will not be possible to downgrade to a previous release.

  • Kafka Reader and Kafka Writer versions 0.8, 0.9, and 0.10 are no longer supported. When you upgrade from Striim 4.x to Striim 5.x, any applications using those versions will automatically be updated to use Kafka Reader 2.1 or Kafka Writer 2.1 (which are backward-compatible with the old versions).

  • As part of upgrading from Striim 4.x to Striim 5.x, a Snowflake Writer with Streaming Upload enabled and Authentication Type set to OAuth or Password will have that property value switched to Key Pair.

  • Starting with release 4.2.0, TRUNCATE commands are supported by schema evolution (see Handling schema evolution). If you do not want to delete events in the target (for example, because you are writing to a data warehouse in Append Only mode), precede the writer with a CQ with the select statement SELECT * FROM <input stream name> WHERE META(x, OperationName) != 'Truncate'; (replacing <input stream name> with the name of the writer's input stream). Note that there will be no record in the target that the affected events were deleted.Handling schema evolution

  • OJet requires Oracle Instant Client version 21.6. See Install the Oracle Instant Client in a Striim server or Install the Oracle Instant Client in a Forwarding Agent.

  • MongoDB Reader no longer supports MongoDB versions prior to 3.6.

  • MongoDB Reader reads from MongoDB change streams rather than the oplog. Applications created in releases prior to 4.2.0 will continue to read from the oplog after upgrading to 4.2.1. To switch to change streams:

    1. Export the application to a TQL file.

    2. Drop the application.

    3. Revise the TQL as necessary to support new features, for example, changing the Connection URL to read from multiple shards.

    4. Import the TQL to recreate the application.

  • Databricks Writer's Upload Policy's default eventcount value has been increased from 10000 to 100000 and the Hostname property has been removed, since the host name can be retrieved using the connection URL. (See Databricks Writer properties.)

Customer-reported issues fixed in release 5.4.2

Striim 5.4.2 also includes all issues fixed in releases 5.2.0 through 5.2.0.8 (see Release notes) and 5.4.0.1 through 5.4.0.6 (see Release notes).

  • DEV-37099: MSJet : cDDL - DDL was not captured through SSMS

  • DEV-38452: for MySQL 8 or later, when a table also includes both a YEAR and an integer type, data may not be read and an onEventDeserializationFailure error will be written to the system log

  • DEV-50091: Striim agent removed from cluster, cause NOT_ENOUGH_SERVERS

  • DEV-51127: Ojet - monitor alert log for error "MISSING multiversion" and create alert for the user

  • DEV-51968: Snowflake Writer : Stage Table Not Found Issue during restart if the app halted due to connection issue during the previous close call

  • DEV-52293: service offline (ThreadLeak)

  • DEV-53123: Striim wizard not listing schemas

  • DEV-53623: Database Reader with DB2 AS/400 fails post upgrade to 5.2.0: [SQL0204] SYSCOLUMNS in SYSIBM type *FILE not found

  • DEV-53761: Apps failed with NOT ENOUGH SERVERS

  • DEV-54064: Oracle Reader Error : 2008 : Failure in executing queries null

  • DEV-54297: Oracle Reader > BigQuery Writer with persisted stream: first event not replayed

  • DEV-55020: potential thread leak for USER_NOTIFICATION_QUEUE back-end token

  • DEV-55035: SalesforceReader: Capture Null values for all columns for all CDC and IL operations by changing SendNullInEvents to true

  • DEV-55464: Striim Cluster Outage Due to High Heap Usage on striim-node-0

  • DEV-55496: mo2data-dev went offline state due to high memory usage

  • DEV-55672: Postgres- Create table with Identity column gets skipped

  • DEV-55683: Salesforce CDC Reader stream preview not displaying events for

  • DEV-55751: Salesforce CDC issues

  • DEV-55817: ROUND_FLOAT function always returning a fixed value of -2.1474836 when value less than -2

  • DEV-55835: Salesforce Reader: Inconsistent values between DB and Salesforce IL

  • DEV-55912: System$OTelMonitoring.OtelMonitoringApp got terminated in Azure production

  • DEV-55940: UI Change- Null values Populated

  • DEV-55943: Import failed - validation of exceptionhandler details failed

  • DEV-56072: OJet - When the capture/apply is in detached state - Trigger HALT through independent thread

  • DEV-56240: Database writer fails with "Mapping of SourceType {java.math.BigDecimal} to TargetType {varchar(12)} is not supported"

  • DEV-56302: Excessive Multi-MB Log Dump on CosmosDB Reader Error (for HTTP 429)

  • DEV-56320: OJet - lag up to 10 minutes

  • DEV-56362: New version of Open Processor can not be loaded in SAAS

  • DEV-56482: SQL Server initial load with always encryption column “is incompatible with nvarchar”

  • DEV-56512: persisted stream replays from latest offset rather than from beginning: as part of this fix, the Kafka consumer property

  • DEV-56533: Source Not Processing

  • DEV-56534: com.webaction.proc.events.WAQueueEvent cannot be cast to class com.webaction.event.Event

  • DEV-56553: Kafka Writer using the Avro Formatter stuck in hang state and eclipse serverlogs flooded

  • DEV-56602: Source saw data but it is not passed to Snowflake Writer after DDL

  • DEV-56689: Spanner PGDialect Writer - KeyColumns forcing a PK_UPDATE

  • DEV-56863: Microsoft 365 - .jar mismatch

  • DEV-56898: application stuck in STARTING SOURCES for more than a day

  • DEV-56922: Striim Server Failing to start with Postgres error after importing 500 applications

  • DEV-56942: PostgreSQL Reader > Database Writer (Oracle) - two records missing

  • DEV-57010: GAX threads cause memory exhaustion in Striim server

  • DEV-57038: App got stuck in Stopping Status

  • DEV-57046: Kafka Writer - delay in drop application due to unexpected topic deletion despite auto create topic being disabled

  • DEV-57088: OJet > persisted stream - data loss

  • DEV-57096: MSJet: ALTER INDEX ... REBUILD PARTITION: Failure in Executing Queries External Exception Partition metadata

  • DEV-57140: OJet:

  • DEV-57145: Ojet - "Invalid Input Number" error due to empty value in NUMBER column

  • DEV-57155: Cluster went offline due to high cpu utilization

  • DEV-57156: Salesforce CDC - Missing metadata fields in update events causing NULL overwrite in target

  • DEV-57168: MSJet SCT ERROR - Invalid ALTER table sub operation

  • DEV-57172: Persisted stream with partition by: Timeout expired while fetching topic metadata

  • DEV-57222: replication factor is not set in the Kafka topic when the property set has 'topicconfig' defined

  • DEV-57288: MSJet Agent crash:

  • DEV-57323: Incremental Batch Reader stopping status 11+ days.

  • DEV-57422: Targets not checkpointing frequently causing source lag and delayed recovery

  • DEV-57432: CI/CD rest api queries randomly timeout and doesnt pass a timely response

  • DEV-57480: CVE 2026 34480 a recently disclosed vulnerability affecting Apache Log4j Core – log4j-core-2.17.2.jar

  • DEV-57509: ClosedChannelException observed on tungsten console exit in Striim v5.4.0.2

  • DEV-57570: When deploying target to agent by mistake, the app runs without error but no data in target.

  • DEV-57584: GG Trail reader fails with java.lang.ArrayIndexOutOfBoundsException: arraycopy: length -2 is negative

  • DEV-57612: return value of com.striim.proc.eventprocessor.ApplicationTemplate.getCheckPointProcessor() is null

  • DEV-57631: Ojet application fails with "Incomplete/unsupported column data while performing SQL parsing"

  • DEV-57654: Parameter in Ojet configuration wasn't reset after it was removed

  • DEV-57778: Apps Getting Stuck in Deploying status

  • DEV-57853: Ojet & OracleReader Type Key Column Mismatch with Oracle Source Table

  • DEV-57859: java.lang.NullPointerException: Cannot invoke "com.webaction.appmanager.AppManager.isAppManagerLeader()" because the return value of "com.webaction.runtime.Server.getAppManager()" is null

  • DEV-58008: JiraReader Initial Load Application Remains in Running State

  • DEV-58038: Kafka Writer - backpressure

  • DEV-58052: Application Deploying status for long time.

  • DEV-58098: Kafka Writer - event distribution & logging bugs

  • DEV-58124: BigQuery Writer - IGNORE EXCEPTION - required field cannot be null

  • DEV-58178: Striim Console Returning Empty Output While Fetching Application Status

  • DEV-58208: Connection issue to Azure SQL Server with Active Directory authentication

  • DEV-58231: Unable to Create New Application Using Automatic Wizard Option and start from scratch

  • DEV-58265: Kafka Writer - missing events due to missing ACLs on the MSK

  • DEV-58300: BigQuery Writer - exactly-once processing (E1P) via BigQuery transactions

  • DEV-58301: BigQuery Writer - implement transaction support in MERGE mode

  • DEV-58352: persisted stream - current thread is not owner of the lock

  • DEV-58357: persisted stream - preserve and log Kafka client exceptions

  • DEV-58422: CheckPointTopic didn't get dropped

  • DEV-58427: Ojet Crash.

  • DEV-58442: Excessive Log Growth Due to Repeated KryoSerializer StackOverflowError

  • DEV-58506: Preserve and Log Kafka Client Exceptions

  • DEV-58507: app with persisted stream hits: Current thread is not owner of the lock

  • DEV-58512: BigQuery IGNORE EXCEPTION - Required field cannot be null

  • DEV-58525: App got stuck in Stopping status

  • DEV-58528: MSJET - support user to override error - delayed durability value to FORCED setting

  • DEV-58545: Ojet - support overriding "InvalidNumber" using property - ReplaceInvalidNumber

  • DEV-58548: Create CDC(OracleReader) app using Wizard failed

  • DEV-58558: BigQuery Writer hits NULL error every 10-15 min, and lag is 8+hrs

  • DEV-58646: Error on INSERT using JSON_OBJECT when Key is present in the event

  • DEV-58661: Initial load applications stuck on Stopping state

  • DEV-58694: SalesforceCDCReader: Inconsistencies in Striim types between Initial Run and Recovery & BitVector support

  • DEV-58713: Oraclereader App - could not be parsed at index 3

  • DEV-58754: Not all the agents are displayed MC cluster

  • DEV-58781: JSON_OBJECT and JSON_ARRAY fail if the USERDATA does not contain the mapped key

  • DEV-58827: MS SQL Reader > BigQuery Writer - initial load in STOPPING state for 18+ hours

  • DEV-58830: CVEs in Striim 5.4.0.2

  • DEV-58833: serverHealthMap returned from REST API doesn't match to mon all output

  • DEV-58834: service is unavailable due to internal service error

  • DEV-58836: MySQL Reader : Index out of bounds Error after restart of striim

  • DEV-58864: OJet Smart Alert , Trigger when Capture process is stuck for more than 10 mins

  • DEV-58918: BigQuery -

  • DEV-58934: Striim Agent - vulnerabilities against log4j version

  • DEV-59014: Issue with Writing JSON Array to JSON Column in Spanner

  • DEV-59038: Google Ads - Enable developerToken as adapter property

  • DEV-59065: SF Reader in IL mode says completed but still there are records to be replicated

  • DEV-59071: MSJet Source BIT Data Type Always Published as false by KafkaWriter

  • DEV-59092: JSON_OBJECTS created at the incorrect level in the nested hierarchy

  • DEV-59116: 431 URL too long error in Salesforce should halt the SalesforceReader instead of failing silently

  • DEV-59139: BigQuery target intermittently fails with backendError during data load

  • DEV-59306: Mongo writer in incremental mode does not show insert operations

  • DEV-59443: Striim Alerts are spammed due to embedded Google image urls

  • DEV-59447: PostgreSQL Reader cddl - Unsupported SQL option(s) for parsing - addColumnIfNotExists

  • DEV-59657: SpannerPG Dialect Writer is ignoring KeyColumns

  • DEV-59689: CDC app ( OJet -> KafkaWriter ) checkpoint didn't change and holds the archived logs

Known issues from past releases

  • DEV-5701: Dashboard queries not dropped with the dashboard or overwritten on import

    When you drop a dashboard, its queries are not dropped. If you drop and re-import a dashboard, the queries in the JSON file do not overwrite those already in Striim.

    Workaround: drop the namespace or LIST NAMEDQUERIES, then manually drop each one.

  • DEV-8142: SORTER objects do not appear in the UI

  • DEV-8933: DatabaseWriter shows no error in UI when MySQL credentials are incorrect

    If your DatabaseWriter Username or Password values are incorrect, you will see no error in the UI but no data will be written to MySQL. You will see errors in webaction.server.log regarding DatabaseWriter containing "Failure in Processing query" and "command denied to user."

  • DEV-11305: DatabaseWriter needs separate checkpoint table for each node when deployed on multiple nodes

  • DEV-17653: Import of custom Java function fails

    IMPORT STATIC may fail. Workaround: use lowercase import static.

  • DEV-19903: When DatabaseReader Tables property uses wildcard, views are also read

    Workaround: use Excluded Tables to exclude the views.