A new release of IBM Streams toolkits is available for download on FixCentral. This package contains the complete set of specialized product toolkits.

You can download Streams Toolkits pack from Fix Central

What’s new?

We continually provide new features and improvements to offer the new functionality, stability, security and privacy in our toolkits.

Here are the most interesting changes:

  • com.ibm.streamsx.eventstore: v2.3.0:
    Client library updated for Db2 EventStore 2.0.0.1
    Third-party library updated to resolve security vulnerability CVE-2019-12402 (netty-all: 4.1.42)
  • com.ibm.streamsx.hbase: v3.8.1:
    The jar library netty-all-4.0.52.Final.jar has been upgraded to netty-all-4.1.42.Final.jar
  • com.ibm.streamsx.inet: v3.1.1:
    Remove opt/downloaded from all lib enties to avoid classpath warnings; Use manifest classpath only
  • com.ibm.streamsx.inetserver: v4.3.1:
    Use relative path for injection form. Resolve #43
    Several typo & minor fixes
  • com.ibm.streamsx.kafka: v3.0.0:
    New features:

    • The included Kafka client has been upgraded from version 2.2.1 to 2.3.1.
    • The schema of the output port of the KafkaProducer operator supports optional types for the error description.
    • The optional input port of the KafkaConsumer operator can be used to change the topic subscription, not only the partition assignment.
    • The guaranteeOrdering parameter now enables the idempotent producer when set to true, which allows a higher throughput by allowing more in-flight requests per connection (requires Kafka server version 0.11 or higher).
    • The KafkaConsumer operator now enables and benefits from group management when the user does not specify a group identifier.
    • Checkpoint reset of the KafkaConsumer is optimized in consistent region when the consumer is the only group member.
    • The KafkaConsumer operator can be configured as a static consumer group member (requires Kafka server version 2.3 or higher).
      See also the Static Consumer Group Membership chapter in the KafkaConsumer’s documentation.
    • The KafkaConsumer operator now uses read_committed as the default isolation.level configuration unless the user has specified a different value.
      In read_committed mode, the consumer will read only those transactional messages which have been successfully committed.
      Messages of aborted transactions are now skipped. The consumer will continue to read non-transactional messages as before.
      This new default setting is incompatible with Kafka 0.10.2.

    Deprecated features:

    • The use of the input control port has been deprecated when the KafkaConsumer is used in a consistent region.

    Incompatible changes:

    • The toolkit requires at minimum Streams version 4.3.
    • The guaranteeOrdering parameter of the KafkaProducer operator is incompatible with Kafka version 0.10.x when used with value true.
      The work-around for Kafka 0.10.x is given in the parameter description.
    • When the KafkaConsumer operator is configured with input port, the topic, pattern, partition, and startPosition parameters used to be ignored in previous versions. Now an SPL compiler failure is raised when one of these parameters is used together with the input port.
    • The default isolation.level configuration of the KafkaConsumer operator is incompatible with Kafka broker version 0.10.x. When connecting with Kafka 0.10.x, isolation.level=read_uncommitted must be used for the consumer configuration.
  • com.ibm.streamsx.messagehub: v3.0.0:
    New features:

    • The included Kafka client has been upgraded from version 2.2.1 to 2.3.1.
    • The schema of the output port of the KafkaProducer operator supports optional types for the error description.
    • The optional input port of the MessageHubConsumer operator can be used to change the topic subscription, not only the partition assignment.
    • The guaranteeOrdering parameter now enables the idempotent producer when set to true, which allows a higher throughput by allowing more in-flight requests per connection.
    • The MessageHubConsumer operator now enables and benefits from group management when the user does not specify a group identifier.
    • Checkpoint reset of the MessageHubConsumer is optimized in consistent region when the operator is the only group member.
    • The MessageHubConsumer operator now uses read_committed as the isolation.level configuration unless the user has specified a different value. In read_committed mode, the consumer will read only those transactional messages which have been successfully committed. Messages of aborted transactions are now skipped. The consumer will continue to read non-transactional messages as before.

    Deprecated features:

    • The use of the input control port has been deprecated when the MessageHubConsumer is used in a consistent region.

    Incompatible changes:

    • Removal of items that have been deprecated in toolkit version 2.x
      • The messageHubCredentialsFile parameter has been removed. Please use the credentialsFile parameter instead
      • The default filename etc/messagehub.json for service credentials is not read any more. Please use etc/eventstreams.json when you want to use a default filename.
      • The default name messagehub for an application configuration is not read any more. Please use eventstreams as name for the application configuration when you want to use a default.
      • The property name messagehub.creds within an application configuration is not read any more. Please name the property for the Event Streams credentials eventstreams.creds.
    • The toolkit requires at minimum Streams version 4.3.
    • When the MessageHubConsumer operator is configured with input port, the topic, pattern, partition, and startPosition
      parameters used to be ignored in previous versions. Now an SPL compiler failure is raised when one of these parameters is used
      together with the input port.
  • com.ibm.streamsx.mqtt: v1.0.3:
    Set system property com.ibm.jsse2.overrideDefaultTLS to true, #5
  • com.ibm.streamsx.sparkMLLib: v1.3.0:
    Remove dependency to SPARK_HOME environment variable
    Switch from operator.xml to annotation based operator model
  • com.ibm.streams.geospatialv2: v3.4.0:
    The operator RegionMatch added
  • com.ibm.streamsx.topology: v1.13.15:
    Several correction and updates – follow the releases on github: Topology Release on GitHub
  • Usage

    Streams Toolkits packs include a complete set of the specialized product toolkits. You can use the packs to upgrade Streams Version 4.3.x. You can bind the toolkits, that the packs include, by using the Streams Studio, by using streams compiler option, by setting the environment variable, or by specifying a toolkits list file.

    Unpacking Streams Toolkits pack:

    1. Extract the contents of the Streams Toolkits pack package files.
    2. For example, to extract the contents of the fix pack on an x86 (64-bit) RHEL 7 system in your repository, for example: $HOME/workspace/toolkits, enter the following commands:
      mkdir $HOME/workspace/toolkits
      tar -zxvf 4.3.1.0-StreamsToolkits-el7-x86_64-i20191212.tar.gz -C $HOME/workspace/toolkits
    3. Bind toolkits in Streams.

    Remark: The original product toolkits are still available in the $STREAMS_INSTALL/toolkits folder.

    Removal if necessary: If you want to remove the Streams Toolkits pack from your environment then delete the pack from the repository on the file system.

Join The Discussion