Creating a Virtual Warehouse

A Virtual Warehouse is an instance of compute resources in Public Cloud that is equivalent to an on-prem cluster. You learn how to create a new Virtual Warehouse in Cloudera Data Warehouse (CDW) Public Cloud.

A Virtual Warehouse provides access to the data in tables and views in the data lake your Database Catalog uses. A Virtual Warehouse can access only the Database Catalog you select during creation of the Virtual Warehouse.

In this task and subtasks, you configure Virtual Warehouse features, including performance-related features for production workloads, such as the Virtual Warehouse size and auto-scaling. These features are designed to manage huge workloads in production, so if you are evaluating CDW, or just learning, simply accept the default values. This task covers the bare minimum configurations.

In subtopics, you see details about how to configure features for production workloads, such as Hive query isolation and Impala catalog high availability.

You obtained permissions to access a running environment for creating a Virtual Warehouse.
You obtained the DWAdmin role to perform Data Warehouse tasks.
You logged into the CDP web interface.
Your activated the environment from Cloudera Data Warehouse.

For more information about meeting these prerequisites, see Getting started in CDW.

Navigate to Data Warehouses > Virtual Warehouses > Create Virtual Warehouse.
In New Virtual Warehouse, specify a Name.

note
The fully qualified domain name of your Virtual Warehouse, which includes the Virtual Warehouse name plus the environment name must not exceed 64 characters; otherwise, Hue cannot load.
Select the Hive or Impala type of Virtual Warehouse you want.
Virtual Warehouses can use Hive or Impala as the underlying SQL execution engine. Typically, Hive is used to support complex reports and enterprise dashboards. Impala is used to support interactive, ad-hoc analysis.
Select the Environment and Database Catalog for this Virtual Warehouse.
In AWS environments only, accept the default availability zone, or select an availability zone, such as us-east-1c.
The default behavior is to randomly select an availability zone from the list of configured availability zones for the associated environment. Generally, it is fine to accept the default. All compute resources run will run in the selected zone.
note
Selection of the zone is not an option in Azure environments.
Select the Hive Image Version or the Impala Image Version version, and the Hue Image version you want to use, or accept the default version (latest) at the top of the drop-down menus.
Select the Size of the Virtual Warehouse as described in the next subtopic.
The AutoSuspend Timeout and Concurrency Autoscaling controls appear.
Configure auto-scaling as described in the subsequent subtopic.
In Authentication, select Enable SSO to enable single sign-on to your Virtual Warehouse, and in User Groups, select a user group set up in advance to access endpoints. If you do not have a user group set up for SSO, do not select Enable SSO.
In Management Console > User Management you set up a user group, required for enabling SSO, that identifies the users authorized to access to this Virtual Warehouse.
Optional: Enter keys and values for Tagging the Virtual Warehouse.
Accept default values for other settings, or change the values to suit your use case, and click Create Virtual Warehouse to create the new Virtual Warehouse.
Click the tooltip for information about settings.

When you create a Virtual Warehouse, a cluster is created in your cloud provider account. This cluster has two buckets. One bucket is used for managed data and the other is used for external data.