Kafka OCF Connector Release Notes¶
Alation Cloud Service Applies to Alation Cloud Service instances of Alation
Customer Managed Applies to customer-managed instances of Alation
January 22, 2025¶
Kafka OCF Connector: Version 24.0.9153¶
Enhancements¶
Support for Both JDBC URI and Configuration Field Values¶
The connector will now read and utilize the connection parameters added in the JDBC URI and in the individual configuration fields (preferred). The value of a parameter configured in the JDBC URI takes precedence over the same parameter configured in the corresponding field in the Connector Settings section of the General Settings tab. (AL-182319)
Memory Optimization¶
Memory allocation for connector operations is now increased to avoid out-of-memory issues. (AL-182319)
Support for MDE Without Broker Connection¶
The connector now supports a new connection property that allows it to only connect to the schema registry for extracting the topics. Earlier, broker authentication details were mandatory.
To enable the schema-registry only connection, set the following properties:
SchemaRegistryOnly: TRUE
ValidateRegistryTopics: FALSE
Setting these values allows you to skip broker authentication details in the connector configuration. (AL-179339)
August 14, 2024¶
Kafka OCF Connector: Version 23.0.8991¶
Enhancements¶
SDK Upgrade¶
The Kafka OCF connector is now upgraded to SDK version 4.8.6.
This upgrade addresses the following Common Vulnerabilities and Exposures (CVEs):
CVE-2022-25647
, CVE-2023-2976
, CVE-2020-8908
, CVE-2021-22569
, CVE-2021-22570
, CVE-2022-3509
, CVE-2022-3510
, CVE-2022-3171
, CVE-2021-29425
, CVE-2021-37136
, CVE-2021-37137
, CVE-2019-20444
, CVE-2021-21290
, CVE-2021-43797
, CVE-2022-24823
, CVE-2024-29025
, CVE-2021-21295
, CVE-2021-21409
, CVE-2020-11612
, CVE-2019-20445
, CVE-2023-34462
, GHSA-xpw8-rcwv-8f8p
.
Docker CIS Benchmark Compliance¶
Kafka OCF connector version 23.0.8991 and newer are now Docker CIS benchmark compliant. (AL-165684)
Fixed Issues¶
Metadata Extraction Fails¶
Metadata Extraction fails due to Java Heap Error.
The issue is now fixed. (AL-168054)