Skip to main content

Striim Cloud 4.1.2 documentation

Release notes

The following are the release notes for Striim Cloud 4.1.2.

What's new in Striim Cloud 4.1.2

Known issue in 4.1.2

The online help links in Striim Cloud will display the documentation for Striim Platform. The Striim Cloud documentation is available at

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

  • Starting with release 4.1.2, the default alerts for server low memory and high disk usage and application halts and crashes have been replaced by a new set of default alerts. After upgrading to 4.1.2, you will need to redo any customizations you made to the old default alerts (see Managing system alerts). If you previously configured alerts for Slack, after upgrading go to the Alert Manager page and click Auto Correct Slack.

  • Starting with release 4.1.2, BigQuery Writer supports the Storage Write API (see BigQuery > Documentation > Guides > Batch load and stream data with BigQuery Storage Write API).

    • When you upgrade from an earlier release of Striim, applications using the BigQuery legacy streaming API will be updated to use the Storage Write API. If for any reason you want to use the legacy streaming API, you may switch back (see the notes on Streaming Configuration in BigQuery Writer properties).

    • Applications using the Load API will not be updated.

  • If you installed the Snowflake JDBC driver, remove it before upgrading to 4.1.2. The required driver is now bundled with Striim Server and the old driver could cause conflicts. The driver is still required if running Snowflake Writer in a Forwarding Agent.

  • Support for Kafka 0.8, 0.9, and 0.10 has been deprecated. Those versions of Kafka Reader and Kafka Writer will still work in release 4.1.2, but support may be removed in a future release.

  • Starting with release 4.1.2, the application state CRASH has been renamed TERMINATED. When upgrading from a previous release, alerts (see Creating and managing custom alerts) with the condition App crashed will automatically be changed to condition App terminated and EXCEPTIONHANDLER (see Handling exceptions) CRASH actions will automatically be changed to STOPPED.

  • OJet SSL configuration: Starting with release 4.1.2, the wallet location is specified in the SSL Config property (see OJet properties). It is no longer necessary to set an environment variable on the Striim server, though if you have done that it will still work (though support for this may be discontinued in a future release).

  • Upgrading if you use OJet: After upgrading and before running OJet, run again as described in Running the OJet setup script on Oracle (if OJet reads from a single primary database or a logical standby) or Configuring Active Data Guard to use OJet (if OJet reads from a downstream database).

  • Handling of underscore characters in Tables and Excluded Tables properties: Underscore characters are now always literal underscores. In previous releases, they were sometimes treated as single-character wildcards, in which cases escaping them with a backslash ()\_) indicated a literal underscore. Also, it is no longer necessary to escape backslashes when Using non-default case and special characters in table identifiers.

  • Importing TQL may fail with missing property errors: In previous releases, any reader, parser, writer, or formatter properties that have default values could be omitted from TQL and on import they would be given those default values. In this release, some TQL that imported without error in previous releases may fail on import due when these properties are not specified. The error message will indicate what property you must add for import to work. This may also happen with sample code in the documentation.

  • Oracle Reader's XStream support has been deprecated.

  • Salesforce Reader : The sObject property has been removed in favor of the new Objects property. If you use the export-import method to upgrade from an earlier Striim release, the value of the sObject property will be copied to the Objects property.

  • Oracle Reader's DDL capture mode has been deprecated in favor of schema evolution: The DDL support described in "Including DDL operations in Oracle Reader output" in the 3.10.3 documentation has been deprecated in Striim 4.x, Oracle Reader's DDL Capture Mode property does not appear in the UI, and creating new applications using this deprecated feature is no longer supported.. Applications created in earlier releases that use this feature are still supported but schema evolution cannot be enabled for those applications. If you wish to migrate from the old feature to schema evolution, you must create a new application.

  • New Halt state & alerts: The new HALT status indicates that an application failure is due to an external cause, such as a source or target database being offline. If you have any alerts on application Crash, you should create additional alerts for Halt. For more in formation, see Sending alerts about servers and applications.Sending alerts about servers and applications

  • BigQuery expects time-partitioned tables by default: By default, starting in 4.0, BigQuery expects target tables to be partitioned by ingestion time or DATE, DATETIME, or TIMESTAMP columns. See "Improving performance by partitioning BigQuery tables" in BigQuery Writer.

  • Oracle Reader transaction buffer defaults have changed: By default, Oracle Reader now automatically buffers transactions larger than 100MB to disk. See "Transaction Buffer Type" in Oracle Reader properties.

Customer-reported issues fixed in release 4.1.2

  • DEV-23078: Oracle Reader ORA-00310 error

  • DEV-24646: GG Trail Parser checkpoint issue

  • DEV-27396: log contains many unneeded INFO level messages from RMIWebSocket

  • DEV-27491: Oracle Reader sending all columns when Compression=True

  • DEV-29118: JMX Reader ""

  • DEV-29662: MON failure in

  • DEV-30421: MS SQL Reader Azure Active Directory authentication failure

  • DEV-30423: DROP failure with JMS Reader

  • DEV-30605: log4j issue

  • DEV-30627: Embed Dashboard button is visible to non-admin user

  • DEV-30921: Oracle Reader issue reading CLOB

  • DEV-30940: monitoring stops updating

  • DEV-31101: S3 Reader error "Unexpected character ('a' (code 97))"

  • DEV-31299: OJet KeyColumns issue

  • DEV-31306: MySQL Reader error "Binlog Client closed abruptlyBinLog"

  • DEV-31397: System$Notification.NotificationSourceApp issue with multiple servers

  • DEV-31398: OJet: can't use property variable

  • DEV-31424: Oracle Reader: LogMiner stops working after DataGuard switchover to physical standby and back

  • DEV-31525: Oracle Reader error "Component Name: xxx. Component Type: SOURCE. Cause: null"

  • DEV-31540: OJet issues with ConnectionURL and DownstreamConnectionURL

  • DEV-31541: OJet issue with database name

  • DEV-31609: MySQL Reader and MariaDB Xpand Reader checkpointing issue

  • DEV-31630: security issue in

  • DEV-31640: Database Reader Sybase > BigQuery Writer issue with BIT type

  • DEV-31641: OJet "Downstream capture: "missing multi-version data dictionary" error

  • DEV-31651: Oracle Reader not using UNIQUE INDEX as key

  • DEV-31711: OJet "Failed to reposition by SCN" error

  • DEV-31878: OJet "Could not find column ... in cached metadata of table" error

  • DEV-32052: OJet issue with BLOB and RAW types

  • DEV-32083: Databricks Writer "HiveSQLException:Invalid SessionHandle" error

  • DEV-32255: GG Trail Reader "ColumnTypeMismatchException" error

  • DEV-32328: OJet java.lang.NullPointerException in server log after undeploy

  • DEV-32415: OJet ORA-01013 error

  • DEV-32485: REST API output for DESCRIBE is incomplete

  • DEV-32501: Mongo CosmosDB Writer is slow

  • DEV-32503: "duplicate key value violates unique constraint 'billing_cycle_uk_idx'" error

  • DEV-32568: Database Reader with SQL Server > BigQuery RWriter ""Invalid datetime string" error

  • DEV-32570: Mongo CosmosDB Reader > Mongo CosmosDB Writer changed ObjectID to String

  • DEV-32582: Oracle Reader > Databricks Writer is missing target acknowledged position

  • DEV-32595: PostgreSQL Reader wildcard issue

  • DEV-32628: Tables property value changed after export-import upgrade from

  • DEV-32822: Web UI slow in

  • DEV-32877: MSSQL Reader issue

  • DEV-32906: MSSQL Reader issue

  • DEV-32915: Database Reader > Database Writer app has NullPointerException error after upgrade from

  • DEV-33043: Oracle Reader > Snowflake Writer "JDBC driver encountered communication error. Message: HTTP status=403” error after auto-resume

  • DEV-33089: Incremental Batch Reader "For input string: "'5475856979'" error

  • DEV-33158: Snowflake Writer java.lang.IndexOutOfBoundsException error after upgrading to

  • DEV-33169: EXPORT does not work with REST API

  • DEV-33175: "Failed to get monitoring data with invalid Token Exception" error with

  • DEV-33286: Oracle Reader > Databricks Writer for Azure Databricks "cannot resolve '`_c0`' given input columns" error

  • DEV-33336: Oracle Reader > Databricks Writer for Azure Databricks has duplicate records in target

  • DEV-33409: OJet does not halt when required archived logs are missing

  • DEV-33492: CPU Utilization 100% with

  • DEV-33534: SMTP configuration issue

  • DEV-33559: CPU Utilization 100% with

  • DEV-33560: PostgreSQL Reader issue with wal2json 2.4

  • DEV-33656: Azure Synapse Writer table "does not exist" error with wildcard when table name includes underscore

  • DEV-34073: Databricks Writer "Integration failed for table" error

  • DEV-34314: SalesForce Reader doesn't capture data when using certain valid Start Time values

Resolved issues

The following previously reported known issues were fixed in this release:

  • DEV-27520: Snowflake Writer can not be used when Striim is running in Microsoft Windows.

Known issues from past releases

  • DEV-6068: 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 correct, 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.

Third-party APIs, clients, and drivers used by readers and writers

  • Azure Event Hub Writer uses the azure-eventhubs API version 3.0.2.

  • Azure Synapse Writer uses the bundled SQL Server JDBC driver.

  • BigQuery Writer uses google-cloud-bigquery version 2.3.3.

  • Cassandra Cosmos DB Writer uses cassandra-jdbc-wrapper version 3.1.0

  • Cassandra Writer uses cassandra-java-driver version 3.6.0.

  • Cloudera Hive Writer uses hive-jdbc version 3.1.3.

  • CosmosDB Reader uses Microsoft Azure Cosmos SDK for Azure Cosmos DB SQL API 4.29.0.

  • CosmosDB Writer uses documentdb-bulkexecutor version 2.3.0.

  • Databricks Writer in AWS uses aws-java-sdk-sts version 1.11.320, aws-java-sdk-s3 version 1.11.320 , and aws-java-sdk-kinesis version1.11.240.

  • Derby: the internal Derby instance is version

  • Elasticsearch: the internal Elasticsearch cluster is version 5.6.4.

  • GCS Writer uses the google-cloud-storage client API version 1.106.0.

  • Google PubSub Writer uses the google-cloud-pubsub client API version 1.110.0.

  • HBase Writer uses HBase-client version 2.4.13.

  • Hive Writer and Hortonworks Hive Writer use hive-jdbc version 3.1.3.

  • The HP NonStop readers use OpenSSL 1.0.2n.

  • JMS Reader and JMS Writer use the JMS API 1.1.

  • Kafka: the internal Kafka cluster is version

  • Kudu: the bundled Kudu Java client is version 1.13.0.

  • Kinesis Writer uses aws-java-sdk-kinesis version 1.11.240.

  • MapR DB Writer uses hbase-client version 2.4.10.

  • MapR FS Reader and MapR FS Writer use Hadoop-client version 3.3.4.

  • MariaDB Reader uses maria-binlog-connector-java-0.2.3-WA1.

  • MariaDB Xpand Reader uses mysql-binlog-connector-java version 0.21.0 and mysql-connector-java version 8.0.27.

  • Mongo Cosmos DB Reader, MongoDB Reader, and MongoDB Writer use mongodb-driver-sync version 4.6.0.

  • MySQL Reader uses mysql-binlog-connector-java version 0.21.0 and mysql-connector-java version 8.0.27.

  • Oracle: the bundled Oracle JDBC driver is ojdbc-21.1.jar.

  • PostgreSQL: the bundled PostgreSQL JDBC 4.2 driver is version 42.4.0

  • Redshift Writer uses aws-java-sdk-s3 1.11.320.

  • S3 Reader and S3 Writer use aws-java-sdk-s3 1.11.320.

  • Salesforce Reader uses the REST API version 53.1.0.

  • Salesforce Writer: when Use Bulk Mode is True, uses Bulk API 2.0 Ingest; when Use Bulk Mode is False, uses the REST API version 53.1.0.

  • Snowflake Writer: when Streaming Upload is False, uses snowflake-jdbc version.3.13.15; when Streaming Upload is True, uses Snowflake Ingest SDK 1.0.2-beta.5.

  • Spanner Writer uses the google-cloud-spanner client API version 1.28.0 and the bundled JDBC driver is google-cloud-spanner-jdbc version 1.1.0.

  • SQL Server: the bundled Microsoft SQL Server JDBC driver is version 7.2.2.