Release Notes for GoldenGate Stream Analytics

1.1.1.8.1 Embedded Ignite Cluster

GGSA implements an Embedded Ignite Cache. Ignite can be used as a target, or a reference for any pipeline, to persist events. In case of GoldenGate, the pipeline persists incoming events containing full record, and also updates the cache with modified events, making available the latest modified records.

You can start or stop the Ignite Cluster from the Cache Cluster tab on the System Settings page.

1.1.1.8.2 NFS Target

GGSA supports a Network File System (NFS) target.

1.1.1.8.3 Ignite Connection

GGSA supports both embedded Ignite cache connection and external Ignite cache connection.

You can enable the internal cache from the Cache Cluster tab on the System Settings page. Enabling internal cache creates and deploys ignite cluster on all spark worker nodes.

You can create a connection to external Ignite by selecting Ignite Cache type, while creating a new connection from the Catalog tab. Provide Ignite server IP address, Port numbers for unsecured cluster, and security credentials for protected cluster.

1.1.1.8.4 Ignite Target

GGSA now supports and uses Ignite as a target to write Json data.

GGSA supports two types of Ignite cluster:

External cluster managed outside GGSA
Embedded Ignite Cluster, started as Spark application and managed by GGSA

With the addition of Ignite target, GGSA can write data to both the internal and external ignite cache calusters.

1.1.1.8.5 Ignite Reference

Ignite reference enriches the stream data with the Ignite cache cluster reference data, at query stage. Ignite reference has data in key-value pair; key is String type and value is a Json object. GGSA supports only single-value equality join in query stage to reference.

1.1.1.8.6 GoldenGate Big Data Connections and Targets

GGSA supports new GoldenGate Big Data connections and targets:

OCI Object Store
AWS S3
HDFS
Microsoft Azure Datalake Gen-2
Hive

1.1.1.8.7 Split Pattern

Use the Split pattern to transform a single event from a stage into multiple events, by splitting the value field. For example, you can flatten an array of json element or json object from the source, to individually process it and also to push it to some targets.

1.1.1.8.8 Cache Monitoring

You can monitor, reset, and reload the caches in both the internal (embedded) and external clusters, using the Monitor option on the GGSA application's homepage.

1.1.1.8.9 Advance Kafka Settings

The Advance Kafka Settings that is added to the System Settings page, enables you to provide Bootstrap URL, SSL truststore, and the SASL information. The bootstrap URL is given preference over the zookeeper, to connect to Kafka, and to even deploy the pipelines.

1.1.1.8.10 Protection Policy

A Protection Policy feature is added under Hadoop Authentication of the Environment tab, on the System Settings page. Protection policy defines how data is transferred between hadoop services and clients (GGSA). Policy types are authentication, integrity and privacy.