StriimĀ® 3.10.3 release notes


For evaluating Striim:

A production environment will require more memory and disk space.

Java SE JDK 7 and OpenJDK 7 are no longer supported. You must upgrade to version 8.

Using Striim with MySQL requires the MySQL Connector/J JDBC driver 5.1.46. If you are using an earlier version, you must upgrade it. See "Installing the MySQL JDBC driver" in the Installation and Configuration Guide.

Striim requires Oracle JDBC driver ojdbc8.jar. If you are using an earlier version, remove it and install ojdbc8.jar. See "Installing the Oracle JDBC driver" in the Installation and Configuration Guide.

The web client has been tested on Chrome. Other web browsers should work, but if you encounter bugs, try Chrome.

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

Writing to Cassandra

If you have an application that uses DatabaseWriter to write to Cassandra, rewrite it to use CassandraWriter. This should require only changing the name of the writer from DatabaseWriter to CassandraWriter.

Writing to Cosmos DB using the Cassandra API

If you have an application that uses DatabaseWriter to write to Cosmos DB using the Cassandra API, rewrite it to use Cassandra Cosmos DB Writer.

Reading from Oracle GoldenGate

GG Trail Reader can read metadata from GoldenGate trail files. See Change Data Capture (CDC) Guide > Oracle GoldenGate > GG Trail Reader properties for instructions on migrating the properties.

File Reader + GG Trail Parser have been deprecated in favor of GG Trail Reader. You may continue to use the FileReader + GG Trail Parser combination used in previous releases but it will not read metadata. GG Trail Parser will be deprecated in a future release. Please contact Striim support to plan a transition.

Google PubSub Writer default property change in

The default values for PubSubConfig have changed. The new values should avoid DEADLINE_EXCEEDED errors. Do not change these values unless instructed to by Striim support.

SQL Server JDBC drivers

SQL Server 2008 requires an older version of Microsoft's JDBC driver that is not compatible with the most recent SQL Server versions. See the Installation and Configuration Guide > Configuring Striim > Insalling third-party drivers > Installing the Microsoft JDBC driver for more information.

Customer-reported issues fixed in release 3.10.3:

Known issues

The following issues have been identified but not yet fixed as of this release. Additional known issues are mentioned in the relevant topics in the documentation.

HTTPReader is missing the Parser menu in the UI (DEV-1854)

Workaround: Use the console or import TQL.

MAP settings are not exposed in the UI (DEV-4138)

The MAP clause of CREATE SOURCE ... OUTPUT TO is not exposed in the UI, though it can be created with the App Wizard.

Workaround: in the console, use DESCRIBE to view settings, ALTER to change them.

WActionStore silently discards events with null value for event type key (DEV-5599)

Creating a source using HTTPReader and DSVParser fails with error (DEV-5916)

Workaround: Have the sender include type=dsv in the URI. For example:

curl -X POST ""...

Dashboard queries not dropped with the dashboard or overwritten on import (DEV-6068)

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.

SORTER objects do not appear in the UI (DEV-8142)

DatabaseWriter shows no error in UI when MySQL credentials are incorrect (DEV-8933)

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.

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

GRANT command wildcard does not work for objects (DEV-12146)

Commands such as GRANT ALL ON * *.* TO ROLE ... will fail.

Workaround: leave out the object element, for example, GRANT ALL ON *.* TO ROLE ....

Import of custom Java function fails (DEV-17653)

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

When DatabaseReader Tables property uses wildcard, views are also read (DEV-19903)

Workaround: use Excluded Tables to exclude the views.

SELECT FROM exception store using JUMPING WITHIN does not work (DEV-23377)

Workaround: omit WITHIN. For example:

SELECT to_waevent(s.relatedObjects) AS evtlist
FROM ExceptionstoreDemo_exceptionstore [JUMPING 5 SECOND] s;