Release Notes for GoldenGate Stream Analytics

1.1.1.8.1 Configure POST and PUT methods in REST Target

REST target can send requests to REST end-point, using HTTP POST and PUT methods. Default setting is POST.

1.1.1.8.2 Kafka Offset Changes

Infer shape from Kafka topic using Earlier/ Latest offset

Detects the shape based on the earliest or the latest offset of the kafka topic. The default option is earliest. Use this option if currently no data is flowing in the topic.

Allow User to reset the offset during pipeline publish

You have two new options on the Pipeline Settings screen:

Input Topics Offset — select the Kafka topic offset value from this drop-down list. Values listed are earliest and latest. The default value is latest. When you publish the pipeline for the first time, the input stream is read based on the offset value you have selected in this drop-down list. On a subsequent publish, the value you have selected here is not considered, and the input stream is read from where it was last left off.
Reset Offset — select this checkbox to read the input stream based on the offset value selected in the Input Topics Offset drop-down list.

Allow User to build dashboard from Beginning or Latest offset

While creating a dashboard, you can build dashboard from the beginning or the latest offset. Available options are latest and earliest . If you select the latest option, the dashboard shows only the new records that have been received after opening the dashboard. If you select the earliest option, then the records are read from the beginning of the OSA pipeline topics.

1.1.1.8.3 Define Key Field while creating a Kafka Target

You can define key fields while defining Kafka Target. Data will be partitioned based on the selected keys.

You can select multiple fields as keys
Key selection is not mandatory
Key selection is allowed only when data format is JSON

1.1.1.8.4 ToJson Pattern

ToJson Pattern transforms event(s) coming from a stage in the pipeline into a JSON text.

Use this pattern to transform multiple events into a single JSON document, and send it to a downstream system through OSA pipeline targets. For example, you can configure a Database target after the toJson pattern stage, to write the json payload (of a single or multiple events), into a database table.

1.1.1.8.5 Condition Expression Builder Enhancements

The Condition Expression Builder enhancements enable you to: -

Create blocks without adding condition expression, which you can add at any later stage
Link the blocks using AND/ OR
Define complex conditions. Example:

1.1.1.8.6 Delete Intermediate Stage(s) from a Pipeline

You can now delete any intermediate Stages in an unpublished pipeline.

Note:

You cannot delete a Source stage.
When you delete any intermediate stage, all its child stages will also be deleted.

1.1.1.8.7 OCI Notification Service

OSA is integrated with OCI notification service, to broadcast messages to distributed components using publish subscriber pattern. This service delivers secure, highly reliable, low latency, and durable messages to applications hosted on OCI, and externally. To integrate with OCI Notification service, you have to define an OCI Notification service topic. You have options to create an ONS type connection and a Notification type target to enable this feature.

Note:

Currently, only JSON data format type is supported for the data to be published.