COVID-19 data lake #

The COVID-19 data lake connects to data found in the Registry of Open Data on AWS. This is a free use of an existing S3 data source that does not require access to an AWS account.

The data lives in S3. Amazon makes public access available without charge and without needing an AWS account. To access this data, connect to the COVID-19 data lake dataset catalog instead of an Amazon S3 data source catalog since the data is publicly accessible.

There is no actual data in the dataset catalog. The dataset catalog provides a connection point to allow you to run CREATE TABLE AS statements and create the data lake tables. Visit the data lake analytics tutorial to utilize the COVID-19 data lake catalog and run an example of these statements.

Configure a catalog #

To create a catalog with the Covid-19 data lake, select Catalogs in the main navigation, and click Configure a catalog. Click on the Covid-19 data lake button in the Select a dataset section.

Define catalog name and description #

The Name of the catalog is visible in the Query editor and other clients. It is used to identify the catalog when writing SQL or showing the catalog and its nested schemas and tables in client applications.

The name is displayed in the Query editor, and when running a SHOW CATALOGS command. It is used to fully qualify the name of any table in SQL queries following the catalogname.schemaname.tablename syntax. For example, you can run the following query in the sample cluster without first setting the catalog or schema context.

SELECT * FROM tpch.sf1.nation;

The Description is a short, optional paragraph that provides further details about the catalog. It appears in the Starburst Galaxy user interface and can help other users determine what data can be accessed with the catalog.

Enter catalog name and description

Connect catalog #

Click Connect catalog, and proceed to set permissions where you can grant access to certain roles.

Set permissions #

This optional step allows you to configure read only access to the catalog.

Click Skip to go straight to adding the catalog to a cluster. If you skip this step, you can add read only access to your catalog for any Starburst Galaxy role later. Skipping this step leaves only the following roles with access to schemas and tables in the catalog:

  • Administrative roles.
  • The currently logged-in role that created the catalog.

Setting permissions grants all specified roles read only access to the catalog. As a result, users have read access to all contained schema, tables, and views.

Use the following steps to assign read access to roles:

  • In the Catalog-level permissions section, toggle the Read-only catalog switch to prevent write access. For catalogs pre-set to read-only, this option is already set to Read-only catalog and disabled.
  • In the Role-level permissions section, expand the menu in the Roles with read access field.
  • Select one or more roles from the list to grant read access to.
  • Click Save access controls.

      Set permissions for read only screenshot

Add to cluster #

You can add your catalog to a cluster later by editing a cluster. Click Skip to proceed to the catalogs page.

Use the following steps to add your catalog to an existing cluster or create a new cluster in the same cloud region:

  • In the Add to cluster section, expand the menu in the Select cluster field.
  • Select one or more existing clusters from the drop down menu.
  • Click Create a new cluster to create a new cluster in the same region, and add it to the cluster selection menu.
  • Click Add to cluster to view your new catalog’s configuration.

      Add to cluster

The Pending changes to clusters dialog appears when you try to add a catalog to a running cluster.

  • In the Pending changes to cluster dialog, click Return to catalogs to edit the catalog or create a new catalog.
  • Click Go to clusters to confirm the addition of the catalog to the running cluster.
  • On the Clusters page, click the Update icon beside the running cluster, to add the catalog.

      pending changes to cluster dialog