1.1.2.6 Release 19.1.0.0.6 - Known Issues
This section lists the known issues and workarounds for GoldenGate Stream Analytics release 19.1.0.0.6.
1.1.2.6.1 Issue with Multiple HDFS Targets in a Pipeline
Issue
GGSA does not support multiple HDFS targets (includes Azure Datalake , which is also an HDFS target type) in the same pipeline, if they are using different HDFS clusters.
Workaround
Create a separate pipeline for HDFS target type.
1.1.2.6.2 MONGODB Test Connection fails for SSL Authentication
Issue
When MongoDB connection is created with Client URI connection type and with SSL authentication mechanism, GGSA Jetty server does not update the certificate and password. The result of Test Connection is based on first certificate and password. Subsequent data is not updated. However, the pipeline deployment works fine.
Workaround
For a valid Test Connection results, restart the Jetty server, each time you test a MongoDB connection.
1.1.2.6.3 Kafka Topic Name cannot contain a Hyphen
Issue
GGSA allows special characters such as - , _, and . in a pipeline name and a stage name. But Kafka does not allow a hyphen in topic names.
Workaround
When a topic is created in Kafka, the hyphen (-) in the topic name is replaced with an underscore (_).
1.1.2.6.4 Pipeline Fails on Publishing with ElasticSearch target and SSL Authentication
Issue
An elastic search connection with SSL type authentication does not mandate username and password, along with trust store credentials. But GGSA uses GoldenGate Big Data (GGBD) API to communicate with Elastic Search. GGBD has implementation bug which mandates username and password along with trust store credentials, making it mandatory to provide both inputs.
Workaround
This is a known issue. When GGDB fixes this issue, user can choose to provide only the truststore credentials, or the username and password for SSL authentication type.