IBM Message Hub Toolkit v1.3.0
The release v1.3.0 is based on Kafka toolkit release v1.3.0 and contains following new features:
- Kafka Client upgrade to version 1.0
- support for SPL
float32
data type for key and message - new operator parameter groupId for the MessageHubConsumer operator. The group ID can now given as a submission time parameter.
- new operator parameter startOffset for the MessageHubConsumer to specify the offset where the operator should start consuming records from.
- The clientId operator parameter is now also available for the MessageHubProducer.
Toolkit documentation (SPL doc) can be found here.
Restrictions:
- The MessageHubConsumer can consume from one topic only when the startOffset parameter is used.
Restrictions compared with the Kafka toolkit v1.3.0
- The MessageHubProducer operator has no parameter consistentRegionPolicy like the KafkaProducer in the Kafka toolkit. The MessageHubProducer always uses the
AtLeastOnce
policy when it participates in a consistent region. The reason for this is that theTransactional
policy of the KafkaProducer requires transaction support on Kafka broker side. The Message Hub cloud service is on Kafka version 0.10.2, which lacks support of transactions.Transactional
consistent region policy will be enabled when the Message Hub service supports Kafka transactions.
Following issues are resolved:
#41 - Confusing error message in case of operator misconfiguration
#40 - Reduce toolkit size
various issues resolved with the underlying Kafka toolkit release
Known issues
- When Kafka's group management is enabled (MessageHubConsumer not in consistent region and startPosition parameter unset or
Default
), the MessageHubConsumer can silently stop consuming messages when committing Kafka offsets fails, see Kafka issue 98. As a workaround, the consumer propertyenable.auto.commit=true
can be used in a consumer property file or app Option.