Release Notes

The Cloudera Altus release notes list the new features introduced and issues discovered in each release.

What's New

The What's New section of the Cloudera Altus release notes lists the new features added in each release.

May 2, 2019

Cloudera Altus has the following new features:
Identity Federation with Altus

If your organization uses an identity provider (IdP) that is compliant with Security Assertion Markup Language (SAML), you can set up identity federation with Cloudera Altus. Identity federation allows users within your organization to log in to Altus through the authentication system in your organization without registering with Cloudera or creating a Cloudera account.

For more information about setting up an identity provider in Altus, see Using an Identity Provider in Altus.

Support for Virtual Machine Scale Sets (VMSS) for Clusters in Azure

In Azure, Altus can create clusters using VMSS. A cluster created with VMSS consists of identical VMs that can be managed as a group. To create clusters with VMSS, Altus requires VMSS roles with the appropriate permissions.

For more information about the roles required for Altus to create clusters with VMSS, see Creating and Assigning a Custom Role.

April 11, 2019

This release of Cloudera Altus has the following new features:
Altus Client 1.6.4

Cloudera Altus Client 1.6.4 includes support for ADLS Gen2 for clusters in Azure.

To upgrade the Altus client to version 1.6.4, use the following command:
pip install --upgrade altuscli 
Support for CDH 6.1

You can create Altus clusters with CDH 6.1, in addition to clusters with CDH 5.x. Cloudera recommends that you upgrade the Altus client to version 1.6.4 if you create clusters with CDH 6.1.

Use the following guidelines when you create Altus Data Engineering or Data Warehouse clusters with CDH 6.1:
  • The CDH 6 release has feature changes that are incompatible with CDH 5.x. CDH 6 also has deprecated or removed support for several components supported in CDH 5.x.

    Before you create Altus Data Engineering or Data Warehouse clusters with CDH 6.1, read the CDH 6 Release Notes and CDH 6.1 product documentation. Workloads that run in clusters with CDH 5.x might not run or might not generate the same results in clusters with CDH 6.

  • Cloudera Navigator integration is not available for Altus Data Engineering clusters with CDH 6.1.

  • Clusters with CDH 5.x and clusters with CDH 6.1 cannot share an SDX namespace.

    You can use a configured SDX namespace for a group of CDH 5.x clusters or you can use a configured SDX namespace for a group of CDH 6.1 clusters, but you cannot use a configured SDX namespace for a group of CDH 5.x and CDH 6.1clusters.

    For information about upgrading a configured SDX namespace to work with CDH 6.1, see Upgrading a Configured SDX Namespace to Work with CDH 6.1 Clusters.

Support for Azure Data Lake Storage (ADLS) Gen2

For Altus clusters in Azure with CDH 6.1, you can use ADLS Gen2 as cloud object store, in addition to ADLS Gen1.

To use ADLS Gen2 for storage, you must upgrade the Altus client to version 1.6.4.

For Altus clusters in Azure with CDH 5.x, you cannot use ADLS Gen2 as cloud object store. You must continue to ADLS Gen1.

Database schema initialization for empty Hive metastore database

When you set up the databases to use for a configured SDX namespace, you do not need to manually create the schemas required to use the database. When you create a cluster that uses the configured SDX namespace, Altus can determine if the database is empty and initialize the database schemas.

For more information about using a configure SDX namespace with a cluster, see Setting up a Cluster with a Configured SDX Namespace.

Option to grant Sentry privileges to the SDX Sentry administrator group

When you create a configured SDX namespace, you can enable the option for Altus to grant ALL Sentry privileges to the SDX Sentry administrator group associated with the SDX namespace.

You might want to select this option if you need to create databases immediately after you create the cluster you use with the configured SDX namespace, such as for testing or demonstration purposes.

For more information about the SDX Sentry administrator group privileges, see SDX Sentry Administrator Group Privileges.

Public IPs option for Altus environments

When you create an environment, you can select the option to allow Altus to assign public IP addresses to clusters created using the environment. If you do not select the option, Altus assigns only private IP addresses to the clusters it creates using the environment.

For more information about the Public IPs environment option, see Enable Public IPs.

To use the option, you must upgrade the Altus client to version 1.6.4.

March 15, 2019

Cloudera Altus supports the following Cloudera JDBC driver:
Impala JDBC Connector 2.6.9 for Cloudera Enterprise

You can use the Impala JDBC Connector 2.6.9 to connect to a secure or unsecure Altus Data Warehouse cluster.

The Impala JDBC Connector 2.6.9 requires only the name of the Altus Data Warehouse cluster and uses the Altus credentials file to get the cluster connection information and verify your login credentials.

You can download the Impala JDBC Connector 2.6.9 for Cloudera Enterprise from the Cloudera JDBC driver download page.

For more information about Altus support for Impala JDBC Connector 2.6.9 for Cloudera Enterprise, see JDBC Connection to Altus Data Warehouse Clusters.

September 19, 2018

This release of Cloudera Altus has the following new features:
Altus Client 1.6.1
The Cloudera Altus Client 1.6.1 includes commands for using the Altus Data Warehouse and Altus Shared Data Experience (SDX) services.
To upgrade the Altus client to version 1.6.1, use the following command:
pip install --upgrade altuscli 

August 23, 2018

This release of Cloudera Altus has the following new features:
Altus Data Warehouse service

The Altus Data Warehouse service enables you to create clusters running the Impala SQL engine to access data in your cloud storage for business analysis and reporting. You can use the query editor in the Altus console to query the data or use standard business intelligence tools with ODBC or JDBC to connect to Data Warehouse clusters to query the data.

For more information about the Altus Data Warehouse service, see Overview of Altus Data Warehouse.

Altus Shared Data Experience (SDX) service

The SDX service provides a consistent view of data for CDH clusters and workloads running on the cloud. Altus SDX enables you to externalize cluster metadata with the Altus SDX namespace. The Altus SDX namespace points to a database that stores metadata for the data accessed by CDH clusters on the cloud, shareable among multiple CDH clusters that access the same data. You can use an Altus SDX namespace for clusters that access data in Amazon S3 or in Azure Data Lake Store (ADLS).

For more information about the Altus SDX service, see Overview of Altus SDX.

Support for CDH 5.15

You can create Altus Data Engineering and Altus Data Warehouse clusters with CDH 5.15.

New Cloudera Altus Service Image in the Azure Marketplace

Cloudera has released a new Cloudera Altus Service image in the Azure Marketplace for CDH 5.15. To use the Cloudera Altus Service Image 5.15, an administrator of your Azure account must agree to the terms of use of the Altus service image in the Azure Marketplace.

For more information about the Altus VM image, see Enabling Programmatic Deployment of the Altus VM Image.

Support for Azure Region Japan East

You can create Altus clusters in the Azure region Japan East.

Contact a Cloudera sales representative for information on Azure Data Lake Storage (ADLS) Gen1 in the Japan East region.

Discontinued Support for SSH private key for AWS clusters.

When you create a cluster in AWS, you must provide a public key instead of a private key. Altus does not support private keys for creating clusters in AWS.

For more information, see Creating a Data Engineering Cluster for AWS and Creating a Cluster for AWS.

August 6, 2018

This release of Cloudera Altus has the following new features:
Support for Groups
You can use groups to manage user access in Altus. You can create a group, add users to the group, and assign roles to the group. All users in a group inherit the roles and resources assigned to the group.
To create and manage groups using the CLI or the Altus SDK, you must upgrade the Altus client to the latest version: Version 1.5.0. Use the following command to upgrade the Altus client to the latest version:
pip install --upgrade altuscli 

For more information, see Altus Groups.

July 26, 2018

This release of Cloudera Altus has the following new features:
ec2:DeleteKeyPair permission optional in AWS cross-account access role
When you set up cross-account access role in AWS for Altus, you do not need to include the ec2:DeleteKeyPair permission. If you include the ec2:DeleteKeyPair permission in AWS cross-account access role, Altus generates a key pair for each Altus cluster that it creates in your AWS account. Otherwise, Altus generates one key pair for all clusters it creates in the same AWS account and region.

For more information, see Key Pair Permissions on EC2.

June 6, 2018

This release of Cloudera Altus has the following new features:
Support for Secure Clusters
You can enable security for clusters in Altus to secure the following components of the cluster:
  • Communication between nodes in the cluster.
  • Communication between Cloudera Manager and the cluster.
  • Data stored in the cluster.

To create secure clusters, you must enable the Secure Clusters option in the environment that you use for a cluster. You must also select CDH version 5.14 or later for the cluster.

To create secure clusters using the CLI or the Altus SDK, you must upgrade the Altus client to the latest version: Version 1.4.1. Use the following command to upgrade the Altus client to the latest version:
pip install --upgrade altuscli 

For more information about the secure cluster option, see Enable Secure Clusters.

May 16, 2018

This release of Cloudera Altus has the following new features:
Support for Microsoft Azure
You can provision clusters and run your data workloads in Microsoft Azure cloud services. Altus can create clusters in a virtual network (VNet) in your Azure subscription and run jobs that read input from and write output to Azure Data Lake Store (ADLS).

For more information about the Azure subscription requirements to create clusters and run jobs on Azure, see Azure Subscription Requirements.

Support for CDH 5.14
You can create Altus clusters with CDH 5.14 in addition to CDH versions 5.11, 5.12, and 5.13.

The CDH versions in Altus clusters support different versions of the Spark service. Altus supports the following combinations of CDH and Spark versions:

For clusters on AWS:
  • CDH 5.12, CDH 5.13, and CDH 5.14 with Spark 2.2
  • CDH 5.11 with Spark 2.1 or Spark 1.6
For clusters on Azure:
  • CDH 5.14 with Spark 2.2 or Spark 1.6
Support for Custom Tags
When you create a cluster in Altus, you can define tags that you want to associate with the cluster instance. When Altus creates the cluster in your cloud provider account, Altus appends the tags to the cluster.

For more information about adding custom tags to the cluster, see Creating a Cluster for AWS or Creating a Data Engineering Cluster for Azure.

April 10, 2018

This release of Cloudera Altus has the following new feature:
Cloudera Altus Trial Account
You can create a free trial account to try out Cloudera Altus and explore how you could quickly provision clusters and run your workloads in the cloud. The Altus trial account gives you 30 days of access to all Altus services that are generally available. You can also request access to Altus services that are in Beta release.

For more information about theAltus free trial, see Getting Started with a Trial Account.

February 22, 2018

This release of Cloudera Altus has the following new feature:
Cloudera Altus SDK for Java
You can use the Cloudera Altus SDK for Java to connect to the Altus Data Engineering service and create and manage clusters and run jobs from your Java application.

For more information about using the Cloudera Altus SDK for Java, see Using the Altus SDK for Java.

January 9, 2018

This release of Cloudera Altus has the following new feature:
Support for Public Key for Cluster Creation
When you create a cluster, you can provide a public key instead of a private key. Altus adds the public key to the authorized_keys file on each node in the cluster.

For security reasons, Cloudera recommends that you provide a public key instead of a private key. The requirement for a private key is now deprecated.

To use a public key for clusters, you must upgrade the Altus client to version 1.3.0. Use the following command to upgrade the Altus client to the latest version:
pip install --upgrade altuscli 

October 31, 2017

This release of Cloudera Altus has the following new feature:
Support for PySpark
Altus supports the Spark Python API (PySpark) in Altus jobs. You can submit PySpark jobs on clusters that run Spark 1.6 or Spark 2.x. To submit PySpark jobs, you must upgrade the Altus client to version 1.2.3.
Use the following command to upgrade the Altus client to the latest version:
pip install --upgrade altuscli 

October 24, 2017

This release of Cloudera Altus has the following new feature:
Support for CDH 5.13
You can create Altus clusters with CDH 5.13, CDH 5.12, or CDH 5.11.

In Altus clusters with CDH 5.13, dynamic partition pruning (DPP) is enabled for Hive on Spark by default. For details, see Dynamic Partition Pruning for Hive Map Joins in the Cloudera Enterprise documentation set.

September 18, 2017

This release of Cloudera Altus has the following new features:
Machine User Accounts
A machine user account provides programmatic access to the Altus API through the CLI. You can use a machine user account in an application to run Altus processes using CLI commands.

For more information about machine user accounts, see Machine User.

Support for CDH 5.12
You can create Altus clusters with CDH 5.12 or CDH 5.11.
The CDH versions in Altus clusters support different versions of the Spark service. Altus supports the following combinations of CDH and Spark versions:
  • CDH 5.12 with Spark 2.2
  • CDH 5.11 with Spark 2.1 or Spark 1.6
Integration with Cloudera Navigator
You can use Cloudera Navigator to generate analytics and data lineage from Altus clusters and workloads. In Altus, select the option to send cluster and workload metadata to an S3 bucket accessible to Cloudera Navigator. In Cloudera Navigator, configure the S3 bucket as a resource for metadata extraction.

To enable integration with Cloudera Navigator using the CLI, you must upgrade the Altus client to the latest version.

For more information about enabling integration with Cloudera Navigator in Altus, see Enable Cloudera Navigator Integration.

For more information about using Cloudera Navigator to generate analytics and data lineage from Altus clusters, see Using Cloudera Navigator with Altus Clusters in the Cloudera Enterprise documentation set.

June 29, 2017

This release of Cloudera Altus has the following new feature:
Altus Client for Windows
You can install the Altus client through pip on Windows. You must install Python and pip before you install the Altus client.

For more information about installing the Altus client for Windows, see Installing the Altus Client on Windows.

June 22, 2017

This release of Cloudera Altus has the following new features:
Workload Analytics
Workload Analytics is a tool that can be used to identify and troubleshoot issues with a job. When you access Workload Analytics through the Altus console, you can view the health checks and baselines for completed jobs that compare the current performance to past runs of the same job as well as the performance of tasks within the same job.

To use Workload Analytics, you must select the Enable Workload Analytics option when you create an Altus environment.

For more information about Workload Analytics, see Workload Analytics.

Support for Spot Instances
If you want to increase the number of nodes in your cluster to improve job performance, you can use Spot instances for compute worker nodes in your cluster. Compute worker nodes are nodes that run computational processes. A Spot instance is an EC2 instance with a low hourly price that you can bid on. Spot instances become available when your bid price is higher than the current market price and they terminate when your bid price is below market price. Using Spot instances allows you to run a large number of job processes on cheaper instances and is a cost-effective way to meet a service level agreement.

For more information about using Spot instances in Altus, see Spot Instances.

Known Issues

Cloudera Altus has the following known issues:
No support for password-protected SSH keys.
Cloudera Altus does not support password-protected SSH keys. When you create an SSH key for use in Altus, do not set a password (or passphrase) for the key. To skip the password prompt, you can use the -N parameter with an empty string. For example: ssh-keygen -N ''
Workload Analytics does not support re-used environment names.
Workload Analytics does not display reports for jobs that run in clusters that use an environment with the same name as a deleted environment.
Workaround: When you create an environment, choose a name that has not been used previously .