PostgreSQL OCF Connector Release Notes¶
Alation Cloud Service Applies to Alation Cloud Service instances of Alation
Customer Managed Applies to customer-managed instances of Alation
November 22, 2023¶
PostgreSQL OCF Connector: Version 1.2.1¶
Enhancements¶
With Alation version 2023.3.4 and PostgreSQL OCF connector version 1.2.0, Alation has introduced an enhanced user interface for configuring the PostgreSQL data source settings.
Note
The connector version is compatible with Alation versions prior to 2023.3.4. However, you will view the old user interface with Alation versions prior to 2023.3.4.
The documentation for the new PostgreSQL experience is available at : PostgreSQL OCF Connector.
The enhanced user interface provides the following features:
Better User Experience¶
The enhanced PostgreSQL user interface provides better navigation and multiple visual cues, making it easy to configure and manage PostgreSQL data source.
Easy to Connect¶
The PostgreSQL user interface now provides a step-by-step process to connect to your PostgreSQL data source easily and quickly.
Additional Error-Prevention Checks¶
The PostgreSQL user interface now includes added checks to avoid obvious configuration mistakes. The user interface also includes text to assist and provide cues while configuring.
Detailed Error Reports and Troubleshooting Support¶
The improved PostgreSQL user interface makes troubleshooting easier for metadata extraction and query log ingestion, as you can now have a detailed error report for both processes. The report contains a detailed error description and steps to resolve the issue. (AL-139424)
November 22, 2023¶
PostgreSQL OCF Connector: Version 1.1.11¶
Compatible Alation version: 2023.1 or higher
Fixed Issues¶
Query Log Ingestion Fails If the Custom Query Does Not Include a transactionid Column¶
From PostgreSQL OCF Connector versions 1.1.9 and 1.1.10 onwards, QLI fails if the Custom QLI Query does not include a transactionid column.
This issue is fixed. Now, in PostgreSQL OCF Connector versions 1.1.9 and 1.1.10 or higher, QLI completes successfully even if the Custom QLI Query does not include a transactionid column. However, Alation recommends that you include the transactionid column in your query to obtain accurate durations for the query.