Skip to main content

Home

4.8.2.0 Release notes

Software version

Release date: November 10, 2023

See 4.8.2.0 for download information.

Software upgrade support

Note

Upgrading is not supported in this release.

For fresh installations, see Installing Unravel.

Certified platforms

The following platforms are tested and certified in this release:

Cloud platforms

  • Google Cloud Platform (GCP) - BigQuery

  • Snowflake

Review your platform's compatibility matrix before you install Unravel.

Updates to Unravel's configuration properties

New features

Improvements and enhancements

  • Upgraded OpenSearch and OpenSearch dashboards to 2.9.0 version. (INSTALL-3348)

  • For enhanced security and permission management, the getData permissions are added to Terraform for BigQuery integration only if the user has opted to enable the Data page or set the Billing data feature. (INSTALL-3414)

  • The command --create-credentials has been replaced with --need-integration to prevent misinterpretation. (BIGQ-795)

  • UI and server Node.js are now upgraded to 18.14.0. (UIX-5577, UIX-5578)

  • Python updated to the latest 3.8.17 version. (INSTALL-3417)

Bug fixes

BigQuery

The following bugfixes are included in this release for Unravel BigQuery:

  • Insights

    • Scheduled query insights are not generated for on-demand queries. (BIGQ-702)

    • The action plan associated with Reservation Insights is missing. (BIGQ-761)

  • Jobs

    • All projects that are configured for Unravel monitoring should be displayed under the Projects page even if the queries or jobs are not run for those projects. (BIGQ-449)

    • When comparing two jobs on the Jobs page, the Creation time is not shown on the Job details page when Show differences is enabled, even though the creation time is different. (BIGQ-615)

Snowflake

The following bugfix is included in this release for Unravel Snowflake:

  • Warehouses

    Unravel (Integration Service) IS queries are preventing the suspension of warehouses in the environment. (SNOW-997)

  • Unravel does not support Billing for on-prem platforms.

  • Monitoring the expiration of the SSL Certificates and Kerberos principals in Unravel multi-cluster deployments.

The following features are not supported for MapR:

  • Impala applications

  • Kerberos

  • The following features are not supported on the Data page:

    • Forecasting

    • Small Files Report

    • File Reports

  • The following reports are not supported on MapR:

    • File Reports

    • Small Files Report

    • Capacity Forecasting

    • Cloud Migration reports

  • AutoAction is not supported for Impala applications.

  • Billing

  • Insights Overview

  • Migration planning is not supported for the following regions for Azure Data Lake:

    • Germany Central (Sovereign)

    • Germany Northeast (Sovereign)

  • Forecasting and Migration: In a multi-cluster environment, you can configure only a single cluster at a time. Hence, reports are generated only for that single cluster.

  • Unravel does not support multi-cluster management of combined on-prem and cloud clusters.

  • Automatic FSImage processing is not supported for multi-cluster environments.

  • Unravel does not support apps belonging to the same pipeline in a multi-cluster environment but is sourced from different clusters. A pipeline can only contain apps that belong to the same cluster.

Snowflake

The following Known issues are included in this release for Unravel Snowflake:

  • Issue: Insights may not be generated in some cases where default_runtime_data_connector_name or default_configured_asset_sqldataconnector is used as the data connector. (SNOW-596)

    Workaround: The default_inferred_data_connector_name is the recommended data connector to use.

    data_connectors:
       default_inferred_data_connector_name:
           class_name: InferredAssetSqlDataConnector
           include_schema_name: false

    For more details, refer to Data Connectors and Configure your individual Data Connectors.

  • Some of the features on the Data page, such as the trend graphs on the Data Overview page and on the Data Tables page, are not applicable for Snapshot mode in Snowflake. (SNOW-1281)

  • Data quality insights are not supported for Snapshot mode. (SNOW-1281)

  • If tables are created with the same name and are accessed, deleted, and re-created, and if those tables are re-accessed, then their query and app count do not match. (DATAPAGE-502)

  • The query to fetch tableDailyKPIs is getting timed out in case of a huge table partition (27 million). (DATAPAGE-740)

  • For Hive metastore 3.1.0 or earlier versions, the creation time of partitions is not captured if a partition is created dynamically.  Therefore, the Last Day KPI for the partition section is not shown in Unravel. (DATAPAGE-473)

  • On the Data page, size data is missing for certain tables in databases, although the partition size is correctly displayed in the Partition Detail section. (DATAPAGE-695)

  • On the Table Details page under the Applications tab, inaccurate data is displayed for a table. This issue occurs if a table is deleted and recreated multiple times and applications executed to access the table before the next cycle of the table worker. (PG-156)

  • The Insights Overview tab uses UTC as the timezone, while other pages use local time. Hence, the date and time shown on the Insights Overview tab and the other pages after redirection can differ. (UIX-4176)

  • Kerberos can only be disabled manually from the unravel.yamlfile.

     kerberos:
          enabled: False
  • WorkloadFit report

    • A large number of tags can cause the Workload Fit report to fail. (PG-265, CUSTOMER-2084)

    • WorkloadFit report > Heatmap: The job count has data, but Vcore and memory are empty. (MIG-262)

  • Inconsistency between the regions displayed on the Unravel user interface and the ones included in AWS EMR. (MIG-280, MIG-281)

  • The Cloud Mapping Per Host migration report fails for some regions. (MIG-303)

  • Cluster discovery

    • The On-prem Cluster Identity might show an incorrect Spark version on CDH. The report may incorrectly show Spark 1 when Spark 2 is installed on the CDH cluster. (REPORT-1702)

  • Queue analysis:

    • The log file name (unravel_us_1.log) displayed in the error message is incorrect. The correct name of the log file is unravel_sensor.log. (REPORT-1663)

  • Cloud Mapping Per Host report scheduled in v4.6.1.x does not work in v4.7.1.0. Users must organize a new report. (REPORT-1886)

  • When using PostgreSQL, the percentage (%) sign is duplicated and displayed in the Workload Fit report > Map to single cluster tab. (MIG-42)

  • SQL events generator generates SQL Like clause event if the query contains a like pattern even in the literals. (TEZLLAP-349)

  • After upgrading to v4.7.1.0, Notebooks do not work. You can configure them separately. (REPORT-1895)

  • After upgrading from v4.6.x to v4.7.1.0, the Tez application details page does not initially show DAG data. The DAG data is visible only after you refresh the page. (ASP-1126)

  • In the App summary page for Impala, the Query> Operator view is visible after scrolling down. (UIX-3536).

  • On the Clusters > Resources page, in the Group By drop-down list, the Application Type, User, and Queue options are duplicated for the YARN/IMPALA resource job type. The issue occurs if identical user-defined tags are used. (UIX-5898)

  • Jobs are falsely labeled as a Tez App for Oozie Sqoop and Shell actions. (PLATFORM-2403)

Snowflake

The following limitations are included in this release for Unravel Snowflake:

Support

For support issues, contact Unravel Support.