Workflow/Jobs page displays empty for Analysis, Resources, Daggraph, and Errors tab. (DT-1093)

Event logs and YARN logs are not loaded for some applications in Google Dataproc clusters. (PG-170)

Incorrect data is displayed in the Number of Queries KPI/Trend graph on the Overview page. (DATAPAGE-502)

Create time of partitions does not get captured in hive metastore if the partition is created dynamically. This limits Unravel to show Last Day KPIs for the partition section.

Wrong data displayed for Number of Partitions Created KPI/trend graph under Partitions KPIs - Last Day section in theData page. (DATAPAGE-473)

Table names are not captured properly in some scenarios for Databricks runtime 8.x and above. (PG-252)

DataBricks jobs are being missed intermittently in Unravel. (PG-232)

Google Cloud Datapro: Executor Logs are not loaded for spark applications. (PG-229)

Exception: Problem when retrieving bootstrap actions for cluster is seen in the aws_worker daemon logs.

Workaround: While creating an AWS account for EMR Chargeback/Insights overview feature, you must include an additional entry in the Policy JSON file for "elasticmapreduce:ListBootstrapActions", as follows:

{
    “Version”: “2012-10-17",
    “Statement”: [
        {
            “Effect”: “Allow”,
            “Action”: [
                “pricing:GetProducts”,
                “elasticmapreduce:ListClusters”,
                “elasticmapreduce:DescribeCluster”,
                “elasticmapreduce:ListInstanceFleets”,
                “elasticmapreduce:ListInstanceGroups”,
                “elasticmapreduce:ListBootstrapActions“,
                “elasticmapreduce:ListInstances”,
                “ec2:DescribeSpotPriceHistory”
            ],
            “Resource”: “*”
        }
    ]
}

Even though the AWS account was already created without this entry (elasticmapreduce:ListBootstrapActions), you can always include this policy later.

Unravel node fails to send email notifications. (INSTALL-1694)

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

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

 kerberos:
      enabled: False

Cloud Mapping Per Host report: Failure to get instance list for certain cloud providers. (MIG-171)

Workaround:

Cluster discovery

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

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

The TopX report email contains a link to the Unravel TopX report instead of showing the report content in the email as in the old reports.

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)

The sensor setup script fails with unrecognized arguments. (INSTALL-1667)

There is a lag seen for SQL Streaming applications. (PLATFORM-2764)

If the customer uses an active directory for Kerberos and the samAccountName and principal do not match, this can cause errors when accessing HDFS. (DOC-755)

In AAD login mode when external logout happens, the user still has access to his current logged-in UI. (UIX-4125)

For PySpark applications, the processCPUTime and the processCPULoad are not captured properly. (ASP-626)

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

Notebooks will not work after upgrading to v4.7.1.0. You can configure them separately. (REPORT-1895)

In case you have configured a single cluster deployment for Unravel and the cluster name is not default, then the Datapage feature may not work properly.

For this, you must explicitly set the following property after upgrading. (INSTALL-2151)

<Unravel installation directory>/unravel/manager stop
<Unravel installation directory>/unravel/manager config properties set hive.metastore.cluster.ids=<cluster-name>
<Unravel installation directory>/unravel/manager apply
<Unravel installation directory>/unravel/manager start

After you upgrade 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)

On the Manage page, the DB Stats are not displayed for untracked clusters. (UIX-4171)

The new user interface (UI) can be accessed only from Chrome.

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

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