StreamBase Release Notes

The following methods in the .NET client API produce incorrect results for Field objects whose type is DataType.TUPLE: Schema::Field::GetHashCode(), Schema::Field::Equals().

None.

If you use the Strict setting for the union operator and strings are not of the same size in the input streams, StreamBase fails to generate a typecheck error. Instead the output uses the size of the larger string.

Avoid specifying strings of different lengths if you use the union operator and strict settings.

If you open a project, open an application in the project, delete the project, and then click the application in the EventFlow editor, StreamBase Studio generates duplicate File Deleted dialog boxes.

Click the same button in both boxes.

Some applications that use dynamic variables may generate the following typecheck error:

Change the dynamic variable to reference an output stream rather than an input stream. You can create an equivalent output stream by connecting the input stream to a Map operator (passing all fields unchanged), then to a new output stream. Use the newly created output stream to update your dynamic variable.

Restore the connection by setting the jdbc-reconnect-regexp parameter of the data-source element to .* (period asterisk) in the server's configuration file. For example:

<param name="jdbc-reconnect-regexp" value=".*" />

Duplicate stream stream-name detected

When this message appears, StreamBase Studio refuses to typecheck the module reference and may prevent you from continuing to develop operators downstream, even if the application has no other errors and is runnable by either StreamBase Server or StreamBase Studio.

org.xml.sax.SAXParseException: Invalid byte 1 of 1-byte UTF-8 sequence

streambase.codegen.intermediate-stream-dequeue-regex=(regex_pattern)

For example, setting the JVM arguments to include:

-Dstreambase.codegen.intermediate-stream-dequeue-regex=Map\\d

allows any intermediate stream that contains the pattern of a Map followed by a digit to be exposed as a dequeueable stream. All other intermediate streams normally available in debug mode will not be available.

One incorrect side effect is that if one predicate in filtered subscribe fails, then predicates that come after it in the list are not executed and tuples are not delivered. Similarly, if other operators are downstream and only one is set for data parallelism, the other operators may not see tuples. Which operators see tuples is effectively non-deterministic.

If you experience the problem described, consider limiting the number of rows that MySQL can read at one time. You can do this by enabling the new jdbc-fetch-size parameter in the data-sources section of the StreamBase server configuration file, and setting it to the Java Integer.MIN_VALUE literal, -2147483648. Note that, although other JDBC drivers interpret a positive jdbc-fetch-size value as a hint, MySQL drivers ignore all values except this magic value. See Using JDBC Data Sources for details.

For example, the following statement passes typechecking even if the named table or fields do not exist in the JDBC data source:

APPLY JDBC DB2 "INSERT INTO mytable (id, name) VALUES({id},
{name})" FROM InStream INTO OutStream;

This applies both to using fields from other schemas, or to using the Field objects that were used to create the Schema. Fields that are used to create a schema are not fully initialized, and so you must get the actual Field from the new Schema object in order to access the fields of a Tuple.

MOZILLA_FIVE_HOME=/usr/lib/mozilla-1.7.3
export MOZILLA_FIVE_HOME