Release Notes 2024.1 (General Availability)

Note

The release notes on this page reflect changes to the Alation application. If you’re looking for OCF connector release notes, jump to Open Connector Framework (OCF) Release Notes.

RELEASE 2024.1.1

build 18.1.0.70857

Released April 4, 2024

Note

This release is available for all Alation instance types: customer-managed (on-premise) and Alation Cloud Service.

New User Experience (Public Preview IV)

​The New User Experience has now moved into Public Preview IV. The following list captures a summary of the additional features and pages currently available in Public Preview IV:

  • Data source catalog details page

  • Schema catalog details page

  • Table catalog details page

  • Column catalog details page

  • Catalog navigation

  • Data source hub

  • Domains Hub and details

  • Homepage basic features and Admin guided user interface (GUI)

  • Query page (with functionality to run the query in the catalog page)

  • BI hub and all detail pages

  • The dynamic template layout in Admin Settings > Customize Catalog > Custom Templates for the BI object types:

    • BI datasource column

    • BI report column

    • BI datasource

    • BI server

    • BI report

    Note

    The dynamic template layout will be available for the Classic User Experience and the New User Experience after the update to the 2024.1.1 release. All cloud-native environments (New User Experience environments) should be updated to this release by May 3, 2024.

  • The ability for Server Admins to make the New User Experience default if desired

  • Search (list and table view, saved search, export results)

    Note

    The More filter experience and other improvements are coming in the 1.0 release of the New User Experience.

  • Conversations

  • Tags object page

  • Backreference group move-ability in templates

  • Lineage (simple layout view)

    • The compound layout view and manual lineage are coming soon

  • Dataflow object page

  • Document hub basics

  • Alation add-ons

    Note

    To participate in the New User Experience Public Preview, you must have Beta language contained in your contract or have a Beta addendum signed. Reach out to your Alation account manager for more information if you would like to access the Preview.

Alation Agent

Alation Cloud Service on Cloud-Native Architecture

For BI sources using Alation Agent in polling mode, an informational message has been added to the Test Connection dialog to inform admin users that the operation may require additional time to complete. (AL-141782)

Domains

Filtering Catalog Content Based on Domain: Alation now allows for a more personalized catalog experience with filtering the left-hand navigation based on users’ domains. The feature is intended to provide quicker access to important information by filtering out data unrelated to domains. (AL-121118)

Governance

Redesign of the Govern Landing Page

In the Apps menu, the Govern tile was renamed to Curate & Govern. The landing page for Curate & Govern was redesigned and now includes tiles for each part of the Governance App. This change has a dedicated flag in alation_conf: enable_governance_home_page_redesign (enabled by default). (AL-147712)

Data Dictionary

Handling of blanks and invalid values: In a downloaded data dictionary, invalid cells are now represented by underscores, replacing the “N/A” and “null” values from the legacy process. In an uploaded data dictionary, blank values now trigger the “unset” operation for existing entries. The Replace Existing Values option also supports the “unset” operation—blank values in the upload will overwrite existing ones if selected; if not selected, existing values will be preserved. (AL-132472)

Lineage

Business Titles in the Compound Layout View: You can now choose to display business titles inside nodes on lineage charts instead of technical names. The option is located in the Filters dialog accessible on the top left of the chart. Business titles are sourced from the Title catalog field of an object. For objects with no Title, their technical names will be displayed. (AL-146600)

Alation Analytics

  • Added the table documenthubs to the Alation Analytics database. Users can now retrieve document hub information and categorize and analyze their document and folder objects by specific document hubs. (AL-150170)

  • Added a new document_hub_id property to the terms and glossaries tables in the Alation Analytics database. Alation Analytics users can leverage this field when retrieving information on a document hub (number of folders, documents, document templates, etc.) (AL-142164, AL-147417)

  • The column rdbms_datasources.uri in the Alation Analytics database will now be populated for OCF data sources. This change specifically accommodates the URI for the GBQ and Hive data sources. (AL-125234, AL-151676)

Alation Public API’s

Find a short summary of the Alation API changes in 2024.1.1 below. More details are available in the API Release Notes on Alation’s Dev Portal.

New My Domains API

The new My Domains API allows Catalog and Server Admins to assign users and groups to domains and more. The API is part of the Federated Catalog public preview. To use it, enable the Enable Federated Catalog Features flag on the Feature Configuration page in Admin Settings. (AL-121118)

Note

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

Domains API

  • Added endpoints to the Domains API to move a domain to a different parent and retrieve a single domain. (AL-121319)

  • The Domains API can now recursively assign domain membership to an object and all its children. (AL-141426)

Cross-System Lineage API

The Cross-System Lineage API endpoints are being merged into the existing Lineage API. The separate Cross-System Lineage API is being deprecated. (AL-145817)

OCF Data Sources API

  • You can now get and update all metadata extraction options for an OCF data source. 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. (AL-149793, AL-148936)

  • 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. (AL-148936)

Relational Integration API

  • The Relational Integration API can now get and update STRUCT columns and child columns. (AL-152225)

  • The Relational Integration API documentation was updated to indicate that the POST methods should not be used to update objects. (AL-146270)

Data Dictionary API

Policy API

The List Policy Groups endpoint now works with a trailing slash. It will also continue to work without a trailing slash. (AL-145478)

Bug Fixes

Curate & Govern

  • Resolved a problem where removing values from Object Sets bypassed the workflow process. Object Set and People Set fields now fully adhere to workflows. (AL-144777)

  • Resolved a discrepancy in the display of Snowflake tag names between Customize Catalog > Custom Fields and Customize Catalog > Custom Field Permissions. Previously, tags shown with fully qualified names in the Custom Fields section were displayed with partial names in the Custom Field Permissions section. Now, tags are consistently displayed with their full names in both sections. (AL-144307)

  • Fixed an issue where email notifications for custom field modifications were sent without considering the custom field’s permission settings. Now, email notifications undergo a permission check so that only users with custom field access are notified of changes. (AL-147500)

Data Dictionary

  • Fixed an issue where updating a custom field through data dictionary uploads wasn’t reflected in field history. Field history will now be correctly updated when a custom field update is done through data dictionary upload. (AL-149122)

  • Fixed an issue preventing the user interface from accepting “N/A” as a valid option for Picker custom fields during data dictionary uploads. “N/A” values are now supported for uploading in Picker fields. (AL-146164)

  • Fixed an issue with the data dictionary upload where blank values led to inconsistent updates: Titles were updated while Descriptions were ignored when the Keep Existing Values option was selected. Now, both the Title and Description fields are updated. (AL-146220)

Alation Analytics

  • Fixed a bug causing the ETL process for Alation Analytics to fail with an error Must be a superuser to terminate superuser process. Now, Alation no longer aborts queries run by super users in Postgres, as it’s not allowed since version 13.13. (AL-148020)

  • Fixed an issue where the deletion of multiple terms using Bulk Utility wasn’t reflected in the Alation Analytics database by subsequent ETL jobs, as the ETL checkpoint failed to recognize the deletions. Now, objects deleted through the Term and Document public API will not alter the ts_updated field, ensuring accurate tracking of deletions. (AL-134334)

  • Resolved a bug where term IDs remained in the glossaries.glossary_links column of the Alation Analytics database after their removal from a glossary. This issue was addressed by modifying the term extraction query to consider the ts_deleted timestamp along with ts_updated. (AL-134089)

Terms, Glossaries, and Documents

  • Resolved a bug with the Terms API where using the PUT method removed all glossary associations within a glossary instead of just the specified terms. Now, only the intended terms are removed. (AL-147499)

  • Resolved an issue causing search facets to still display folders and document templates after disabling the Document Hubs 3 feature flag. With this fix, document hub-related search facets are no longer shown in search filters after disabling the Document Hubs feature. (AL-151800)

  • Fixed an issue causing the document templates to still be displayed in the list of term types in Customize Catalog > Custom Templates disabling the Document Hubs feature. Now, only term types for terms will be displayed in Customize Catalog > Custom Templates if the Document Hubs feature is disabled. (AL-149245)

Rich Text Fields Formatting

  • Fixed an issue that caused the loss of formatting when indented text, rows, or cells copied from MS Excel were pasted into the Rich Text editor for articles. Formatting is now preserved as expected. (AL-145495)

  • Fixed an issue where during the editing of a lengthy article, adding a carriage return caused the cursor to jump to the top of the article. (AL-129702)

  • Fixed an issue where formatting in Rich Text fields updated through a catalog set wasn’t rendered correctly on catalog pages of objects in the set. Resolved by adding the necessary classes to properly render the formatting. (AL-103510)

  • Resolved a rendering issue where the ampersand symbol (&) in object titles was not displayed correctly. (AL-71755)

The Connect Platform

  • Resolved a bug causing cross-system lineage between two SQL Server data sources to link to soft-deleted records after metadata extraction. Cross-system lineage will now create correct associations with existing objects in the catalog. (AL-148764)

  • Fixed an issue where partition keys (part of table metadata) were not extracted by the OCF connector for Impala on CDP. Updated table extraction logic in the connector code to include extraction of partition keys. (AL-147592)

  • Fixed an issue with extraction from DB2 sources. Previously, metadata extraction failed with an error MissingFormatArgumentException: Format specifier ‘%s’. To fix the issue, the OCF SDK for the DB2 OCF connector was upgraded to version 4.4.0. (AL-147543)

  • Fixed an issue where metadata extraction failed for an SSRS OCF BI source with the ArrayOutOfBoundException exception. (AL-146517)

  • Resolved an issue in the OCF SQL Server connector where the value title lookup was not functioning with dynamic profiling. The catalog attribute page’s title lookup feature has been updated to support value title lookup when dynamic profiling is enabled. (AL-131988)

Other Fixes

  • Fixed an issue where administrator users were unable to check the status of Alation services with the alation_action status_alation command after updating to version 2024.1. This command now requires execution as the alation user. (AL-150411)

  • Fixed an issue where after upgrading to 2023.3.5, search export containing glossary term objects failed with an error Failed to prepare download: ‘NoneType’ object is not iterable in the logs. (AL-148667)

  • Fixed an issue where switching object types while in the saved search view changed the column selection to default for the saved search. (AL-127725)

  • Resolved an issue where canceling a query for a Hive data source prevented subsequent queries from being executed due to concurrent query checks. This was fixed by adding a cancellation check alongside the concurrent queries check. (AL-142466)

  • Made a change to the internal server API forbidding direct POST requests to the URL /data/0/upload_docs. Now, valid otype and oid are required for this URL, which then enforces restrictions on file types. (AL-137774)

PATCH RELEASE 2024.1.0.1

Alation Cloud installer build 9.0.0.19815

Released March 26, 2024

Note

This release is available for Alation Cloud Service instances that haven’t been migrated to the cloud-native architecture.

  • Resolved a bug in the Open Connector Framework affecting the Test access operation for metadata extraction and query log ingestion. This issue impacted OCF connectors for Snowflake, Oracle, and MicroStrategy, where Test access failed displaying a KeyError['podIP'] error in the user interface and an error Stream closed with status: Status{code=UNIMPLEMENTED, description=Method not found: grpc.health.v1.Health/Check, cause=null} in the logs. The problem was caused by an internal race condition when an operation was requested from OCF connectors. (AL-151828)

RELEASE 2024.1.0

build 18.0.0.66893

Released March 4, 2024

Note

This release is available for all Alation instance types: customer-managed (on-premise) and Alation Cloud Service.

New User Experience (Public Preview III)

Alation Cloud Service on Cloud-Native Architecture

​​The New User Experience has now moved into Public Preview III. The list below captures a summary of the major features and pages currently available in the New User Experience:

  • Data Source Catalog Details page

  • Schema Catalog Details page

  • Table Catalog Details page

  • Column Catalog Details page

  • Catalog Navigation

  • Search List View

  • DataSource Hub

  • Domains Hub and Details

  • Homepage basic features + Admin Guided User Interface (GUI)

  • Query Page (without functionality to run the query in the catalog page)

  • BI Hub and all detail pages

Note

To participate in the New User Experience Public Preview, you must have Beta language contained in your contract or have a Beta addendum signed. Reach out to your Alation account manager for more information if you would like to access the Preview.

Document Hubs (Public Preview)

This release introduces document hubs, designed to enhance your organization’s ability to categorize and manage extensive, written content directly related to your data. Document hubs offer the flexibility to create customized documents, tailored to meet your organization’s data documentation needs.

Document Hubs are set to eventually replace the current articles functionality.

Check out the documentation for Document Hubs.

Key Features

  • Centralized data documentation: Each document hub serves as a dedicated space within the catalog for organizing your written content.

  • Structured organization: Document hubs consist of a hierarchical structure with hubs at the top level, followed by folders, and documents within those folders. This structure facilitates easy navigation and management of content.

  • Management of content: Administrators have the capability to create and publish document hubs. Users can configure folders, add or remove documents, modify titles and descriptions, and utilize search and sorting functionalities. (AL-143825, AL-142897)

Note

Document hubs are available as part of Alation’s public preview program. To participate in the Document Hubs Public Preview, you must have Beta language contained in your contract or have a Beta addendum signed. Reach out to your Alation account manager for more information if you would like to access the Preview.

Lineage

Lineage Compound Layout Is General Availability

The Compound Layout lineage view, initially launched into public preview in version 2022.3.0, is now a General Availability offering for all customers in all environments. The “Beta” label was removed from the Compound Layout view switch on lineage graphs.

Note

The Compound Layout view organizes objects on lineage graphs into groups under data sources, such as Snowflake or Tableau, enabling focused analysis of data movement across different platforms. Users have the capability to drill down from the data source to column level, tracing objects across data source groups and achieving a comprehensive end-to-end lineage view.

Limitation & Workarounds

There is still a performance limitation in the Compound Layout view feature, where lineage graphs with a large number of objects may experience slow initial loading times. We’ve prioritized efforts to resolve this issue in the upcoming releases.

If you run into this issue, you can use the following workarounds until the issue is resolved:

  • Adjust graph limits: Ask your Alation Server or Catalog Admin to adjust graph limits and try reloading the graph with the Compound Layout disabled.

  • Clean up the lineage graph: Disable the Compound Layout, and in the default legacy view, remove unnecessary lineage and dataflows either manually or via APIs. Enable the Compound Layout view and reload the graph.

  • Request a targeted node cleanup: Reach out to Alation Support for targeted node cleanup.

  • Revert to the default view: If a graph’s loading time exceeds 30 seconds or fails, refresh the page, revert to the default view, and attempt to reload with the Compound Layout view disabled.

  • Try out optimized graph display: Alation Cloud Service customers can request evaluation of a new beta feature for optimized graph displays. Contact Alation Support to have it enabled on your Alation instance.

Beta Features Within Compound Layout

Some elements of the Compound Layout view are still marked with a “Beta” label, as they remain in public preview:

These features have recently transitioned from private to public preview as we seek broader feedback before finalizing their release.

Manual Lineage in Compound Layout (Public Preview)

We’ve added an Edit button directly in the Compound Layout view of lineage graphs. The button enables users to manually create, publish, and, if necessary, delete lineage. The feature is still in public preview, as the user interface for previewing manual lineage and data source grouping is still under development. As a temporary measure, upon publishing manual lineage, users are redirected back to the compound layout to review their modifications within the established data source groups. Users also have the flexibility to refine their manual lineage as needed after reviewing the graph. (AL-145095)

Data Trust Overlay (Public Preview)

We’ve enriched the lineage diagrams with the overlay summary pane designed to provide users with quick access to key information. By clicking the overlay icons like depreciation, endorsement, or warning symbols, users can view a pop-up summary containing asset descriptions, steward contacts, trust flag messages, and impact analysis. The feature is still in public preview (beta), with more details and additional overlays to come later based on user feedback. (AL-141586)

General SQL Parser Upgrade

The General SQL Parser’s JAR file was upgraded to version 2.8.5.8 to take advantage of the bug fixes and improvements in the newer version. (AL-143872)

Enterprise Readiness

Postgres Upgrade to 13.13

Upgraded Alation’s internal database (PostgreSQL) to version 13.13 to take advantage of new features and to fix vulnerabilities. (AL-143302)

Apache Kafka Upgraded to 3.6.1

Upgraded Alation’s internal event streaming platform (Apache Kafka) to version 3.6.1 to take advantage of new features and to fix vulnerabilities. (AL-143661)

Chroot Removal

Alation Cloud Service on Cloud-Native Architecture

The Alation Cloud Service instances no longer use the Chroot-restricted environment in their builds. (AL-105007)

Note

This change does not impact customer-managed installations, which will remain unchanged.

Authentication

Reauthentication Due to Inactivity

Alation Cloud Service on Cloud-Native Architecture

Starting with this release, when a user session remains inactive for a predetermined period, it will be automatically terminated. Users receive a warning two minutes prior to session expiration. For FedRAMP deployments, the inactive timeout is fixed at 15 minutes and cannot be adjusted. For non-FedRAMP deployments, the timeout interval can be configured as follows:

  • Default duration: 60 minutes

  • Minimum duration: 5 minutes

  • Maximum duration: 1440 minutes (24 hours) (AL-125476)

Cross-Account IAM Support for AWS Secrets Manager

The authentication support for AWS Secrets Manager has been expanded to include cross-account IAM roles, in addition to the existing methods of IAM user and IAM user+IAM role. The Authentication Configuration Methods for External Systems section of the user interface (Admin Settings > Server Admin > Authentication) has undergone some enhancements for AWS Secrets Manager. Only the relevant configuration fields are now displayed, ensuring a more intuitive user experience. (AL-119588)

Alation Analytics

Alation Analytics PostgreSQL Upgrade to 13.13

The Alation Analytics PostgreSQL database was upgraded to version 13.13 to take advantage of new features and to fix vulnerabilities. (AL-143302)

Information About Tables and Columns Linked to Data Policies Added to Alation Analytics

As of version 2023.1.7, Alation Analytics has supported querying data policies directly from the data_policy table. This enhancement introduces a new table, data_policy_link, which provides detailed associations between data policies and specific table or column objects. This table can be particularly useful for administrators and analysts looking to understand the application of data policies at the granular level of tables and columns.

Columns
  • dim_load_id, dim_ts_created, dim_checksum—ETL bookkeeping columns.

  • object_id, object_uuid—Object ID in numeric and UUID formats respectively.

  • object_type, object_type_id—Object type in the text (table, attribute) and number (27, 1) formats respectively.

  • id—Primary Key for the table in Alation Analytics.

  • policy_link_id—Internal ID for each policy link.

  • policy_id—Policy ID.

  • ts_created, ts_updated, ts_deleted—The created, updated, and deleted timestamps.

  • deleted—Boolean to denote if a link is soft-deleted. (AL-139218)

Expire Old WAL Archives

A new scheduler will now automatically remove WAL archives of the Alation Analytics database that are older than 48 hours. This change is designed to save disk space by ensuring that WAL archives are regularly rotated and outdated files are efficiently purged. (AL-139378)

Transition from Redis to Amazon Elasticache

Alation Cloud Service on Cloud-Native Architecture

Alation Analytics now utilizes cache from Amazon Elasticache instead of Redis within the Alation core container. This is a significant enhancement in the Alation Analytics architecture, aiming to provide a better and more reliable service to Alation Cloud customers. (AL-141201)

Governance

Resolution of Duplicate Tag Names

The display of Snowflake tags on catalog pages (including schema, table, and column pages) has been enhanced for better handling of tags with duplicate names across different schemas:

  • A new feature flag, alation.feature_flags.enable_snowflake_tag_filtering_by_schema, has been introduced to allow optional filtering of tags by schema within catalog pages (disabled by default).

  • The Custom Fields section under Customize Catalog now displays schema information for each Snowflake tag within picker fields. This addition is intended to help users differentiate between tags with identical names but belonging to different schemas. (AL-138710)

Auto-Enablement of Policy Center and Snowflake Tags Backend Parameters

Starting with this release, when the feature flags for Policy Center and Snowflake Tags are enabled in Feature Configuration, the corresponding set of backend flags is also automatically enabled. This enhancement eliminates the need for additional manual backend configuration when enabling the Policy Center and Snowflake Tag features in the Alation user interface. The following backend flags are auto-enabled:

  • alation.ocf.mde.policy.enable_extraction

  • alation.ocf.mde.policy.enable_ingestion

  • alation.ocf.mde.policy.enable_search

  • alation.ocf.mde.policy.enable_sync

  • alation.ocf.mde.custom_field.enable_sync

  • alation.ocf.mde.custom_field.enable_extraction

  • alation.ocf.mde.custom_field.enable_ingestion (AL-143847)

OCF Connectors

Updates to the Open Connector Framework (OCF) connectors are released every week. See Open Connector Framework (OCF) Release Notes for information on the updates in the month of February 2024.

A few February highlights are:

Bug Fixes

Governance & Glossaries

  • Fixed an issue where uploading a data dictionary with custom field names in Japanese failed after upgrading to version 2023.3.3.1. The original parsing limitation to ASCII characters has been expanded to accept Unicode characters, ensuring successful uploads for Japanese and other Unicode characters. (AL-141572)

  • Fixed an issue where titles remained unchanged during a data dictionary file upload when the Keep Existing Values option was selected and the initial title and description values were blank. The fix ensures that titles are now updated correctly when the Keep Existing Values option is selected when the current titles are blank. (AL-146220)

  • Removal of field from an object set is now honored via workflows. (AL-144777)

  • Fixed an issue where manual catalog set synchronization failed with the error Job is not running. It might have been killed or crashed unexpectedly or there might have been a system outage. The fix is expected to lead to reduced job failures in catalog sets synchronization (AL-140909).

  • Resolved an issue where changing the term template via the Bulk Utility did not update the template. The Bulk Utility now supports template updates effectively. (AL-143246)

  • Fixed an issue in the Bulk Utility where the downloaded terms showed deleted objects in Object Sets. Specifically, when columns related to a term’s Object Set custom field Related Objects were dropped and subsequently soft-deleted during metadata extraction, they would still appear as [GONE] in the field history, despite being absent in the user interface. The Bulk Utility has been updated to exclude deleted objects from Object Set values. (AL-136475)

  • Resolved an issue introduced in version 2023.3.1.1 where HTML tags were visibly displayed in the glossary term pages within the Related Terms section. This fix ensures that HTML tags no longer appear on catalog pages for Object Sets. (AL-137238)

  • Resolved an access issue where users with the Steward roles were unable to use the data dictionary public API. Now, when the alation.feature_flags.disable_perm_check_on_upload_dd feature flag is set to False, users in the Steward, Composer, Source Admin, Catalog Admin, and Server Admin roles are allowed to make data dictionary public API calls, including uploading and retrieving task details. (AL-144523)

  • Resolved an issue where workflows reviewer selection was failing on specific instances when user tried to select group as reviewers (AL-145175)

Alation Analytics and Analytics Experience

  • Resolved a synchronization issue affecting column objects’ data between Alation and Alation Analytics, specifically for column titles and descriptions updated through data dictionary upload. To reload the title and description missing data, Reset ETL Checkpoint for the RDBMS Tables. (AL-143810, AL-146271)

  • Fixed an issue in the rosemeta_allvisits table where updates for conversation visits were not accurately reflected. Enhanced the logging mechanism for tracking visits to the conversation page in the public.visits table within Alation Analytics. This fix ensures that all user visits to conversations are properly logged and updated. (AL-142986)

  • Resolved ETL process failures that began following an upgrade to version 2023.3.2.1 and were manifested through the error TransformManager.transform(): Column name not supported in Snowflake: ACCOUNT. To address the incompatibility with Snowflake’s reserved keywords used as custom field names (ACCOUNT), we’ve implemented a solution to rename the affected columns in tables to the format <CUSTOM_FIELD_NAME>_<ID>, ensuring successful data loading into Snowflake without errors. (AL-142557)

  • Fixed an issue where transform containers failed to restart in a healthy state after an unattended server reboot. This fix ensures a coherent and reliable startup of all necessary containers post-reboot. (AL-136558)

Lineage

  • Resolved an issue where upstream column-level lineage links (CLL) failed to generate for certain tables with quoted column names, although downstream lineage remained unaffected. With this bug fix, we’re ensuring upstream lineage visibility for columns with quoted names. (AL-140987)

General SQL Parser

  • Fixed lineage parsing issues between dbt and Snowflake. The fix ensures lineage accuracy from constructs like the CONNECT BY subclause. (AL-144356)

  • Fixed an issue where Google BigQuery published queries were not associating with their respective tables, resulting in their absence from the Queries tab. This fix ensures that Google BigQuery published queries correctly link to tables. (AL-141819)

  • Resolved a parser error affecting Snowflake DDL views, where lineage for views defined and ingested by MDE was not displayed, although connections to related Tableau objects were visible. This update addresses parsing issues, including those related to the CONNECT BY subclause, ensuring accurate lineage representation for Snowflake DDL views. (AL-140906)

Connected Sheets

  • Addressed the Excel login error encountered on Chrome, which was caused by changes to third-party cookie handling. (ACS-562)

  • This fixes the issue where the connected sheets hub page redirects in loops because of chrome’s third-party cookie changes (ACS-589)

Connect Platform

  • Fixed an issue with Hive data sources where, after canceling a query within a session, subsequent queries failed to execute due to concurrent query checks. This fix introduces a cancellation check alongside the concurrent queries check, ensuring smooth execution of subsequent queries after a cancellation event. (AL-142466)

  • Fixed an issue where profiling failed for an AWS Databricks data source with the following error: The connector was provided with a list of columns to profile from a table, however the schema of the returned result set did not match those columns. The solution skips tables that cause failures and continues with the sampling process, ensuring profiling tasks complete successfully. (AL-141595)

  • Addressed an issue where multiple installed versions of a connector on an Alation instance were indistinguishable in the user interface due to the absence of version numbers. This led to confusion over which version was being selected. Now, in case multiple connector versions are installed, the dropdown shows the connector version next to its name. (AL-146195)

Other Fixes

  • Fixed an issue where content such as @-references, links, and photos included in user profile descriptions disappeared upon saving. The fix ensures that all content added to profile descriptions is saved. (AL-143451)

  • Resolved a deadlock issue in uWSGI worker threads introduced by the upgrade from Python 3.6 to 3.9. The deadlock occurred when threads loaded a Django application alongside the Python module traceback. From version 2024.1 onwards, this is addressed by disabling traceback by default. (AL-141594, AL-145955)