Looker OCF Connector Release Notes¶
Alation Cloud Service Applies to Alation Cloud Service instances of Alation
Customer Managed Applies to customer-managed instances of Alation
March 26, 2025¶
Looker OCF Connector: Version 2.1.2¶
Fixed Issues¶
Extraction Fails for Explores with Names Containing Capital Cases¶
The connector fails to extract Explores, which contain capital cases in their names.
This issue is now resolved. (AL-184840)
Missing Connection Objects for Explores with Many Fields¶
Some of the connection objects are missing for Explores with many fields.
This issue is resolved. Explore Query API is now split into smaller chunks to retrieve all connection objects for Explores. However, Explores with many fields now have multiple connection queries instead of one. This is a known API limitation from Looker. (AL-181666)
October 09, 2024¶
Looker OCF Connector: Version 2.1.0¶
Enhancements¶
Support for Cataloging for Explores and Looks Fields¶
Supports cataloging Explores as BI datasources and Looks fields. Each Explore is cataloged as a datasource, has its own Fields and Connections, and is available as part of lineage.
Support for Column-Level Lineage¶
Supports lineage at the column level for the following RDBMS data sources:
Amazon Redshift
MySQL
Microsoft SQL Server
Oracle
PostgreSQL
Snowflake
Note
Enable the connector setting Extract superseded (legacy) objects with type as LookML and Datasource to extract older objects that were phased out and are now embodied with Explores. These older objects will be available in catalog pages (not in lineage). By default this setting is disabled (Recommended).
(AL-164600)
May 22, 2024¶
Looker OCF Connector: Version 2.0.2¶
Enhancements¶
Update to Looker API¶
As per of the notice from Looker, Alation has updated the query_id in the GET /queries/<query_id> API now uses a slug value instead of a numeric value. (AL-147590)
Note
There are no impacts to any of the features supported by the Looker OCF Connector.