See Finding Your Alation Version for help determining which version of Alation you're using.

2024.1.1 API Release Notes

New

My Domains (Federated Catalog public preview)

• As part of the Federated Catalog public preview, we've added the My Domains API, which allows Catalog Admins and Server Admins to assign users and groups to domains. Users can then filter the catalog navigation and search based on those domains. To use this API, you must have turned on Enable Federated Catalog Features on the Feature Configuration page in Admin Settings. (AL-121118)

  📘

  Federated Catalog public preview

  To participate in the Federated Catalog public preview, you must have Beta language contained in your contract or have a Beta addendum signed.

Updated

Domains

• We added endpoints to move a domain to a different parent and retrieve a single domain. The new endpoints can be used by Catalog Admins and Server Admins. (AL-121319)
• The Domains API can now recursively assign domain membership to an object and all its children. (AL-141426)

Cross-System Lineage

• The Cross-System Lineage API endpoints are being merged into the existing Lineage API, and new endpoints have been added for bulk operations as well as operations on individual resources. (AL-145817)

OCF Data Sources

• You can now get and update all metadata extraction options for an OCF data source. Previously, you could only work with a small set of options. The additional options are accessible through a new configuration_parameters body parameter. (AL-148936)
• When updating metadata extraction options, you can now Base64 encode parameter values, enabling you to send multi-line SQL queries, for example. To do this, make sure the base64 parameter is set to true in your JSON payload. (AL-149793, AL-148936)

Relational Integration

• The Relational Integration API can now get and update STRUCT columns and child columns. (AL-152225)
• We updated the Relational Integration API documentation to indicate that the POST methods should not be used to update objects. When using the POST methods, certain attributes will be set to a default value when not included in the request. This applies to Create new columns under a particular data source, Create new schemas under a particular data source, and Create new tables under a particular data source. (AL-146270)

Data Dictionary

• We've added an endpoint to get data dictionary task errors so you can see what might have cause a data dictionary upload to fail. (AL-150783)

Fixed

• For consistency with other APIs, the List Policy Groups endpoint now works with a trailing slash. It will also continue to work without a trailing slash. (AL-145478)

Known Issues

There is a known issue with the Get schemas endpoint where using a name value with capital letters will return no content despite giving a 200 response code. Using a name value with all lowercase will return schemas even when the schema name included capital letters. This has been fixed in 2024.3.1. (AL-156656)

Deprecation Notices

Upload Logical Metadata (ULM) API

The ULM API will be deprecated in release 2024.3.1 in early October.

If you are using the ULM API, we recommend you move as soon as possible to using the newer, more performant Custom Field Values Async API or one of the other alternatives for your use case as shown below.

Why is this happening? Alation is investing in scalable APIs and infrastructure that are no longer compatible with the ULM API. To give our customers the best experience, we will be focusing our efforts on more scalable alternatives as shown in the table above.

Custom Field Values Synchronous PUT

The PUT multiple Custom Field Values synchronous endpoint will be deprecated in release 2024.3.1 in early October. As an alternative, migrate to the PUT multiple Custom Field Values Async endpoint as soon as possible. The asynchronous endpoint is much more performant and provides a better experience.

OCF Data Sources API Parameters

For the Trigger metadata extraction job endpoint of the OCF Data Sources API, we will be deprecating the three body parameters limit_schemas , exclude_schemas, and remove_filtered_schemas. The deprecation will occur in release 2024.3 in early September. As an alternative, we recommend you use the Update metadata extraction configurations endpoint to configure the extraction and use the Trigger metadata extraction job endpoint to run the extraction. (AL-148936)

Cross-System Lineage API

The separate Cross-System Lineage API is being deprecated immediately, and its endpoints are being merged into the existing Lineage API.