Many of the examples use a sample river flow data set. USGS Surface-Water Data Sets are provided courtesy of the U.S. Geological Survey.
To run the examples, you must first setup a small object store for the data set.
Your external object store must be configured to allow Advanced SQL Engine access.
When you configure external storage, set the credentials that will be used in SQL statements by Advanced SQL Engine. The supported credentials for USER and PASSWORD (used in the CREATE AUTHORIZATION command) correspond to the values shown in the following table:
|Amazon S3||Access Key||Secret Access Key|
|Amazon S3 IAM||AWS Identity and Access Management (IAM) Credentials (roles/policies)|
|Azure Access Key||Storage Account Name||Key|
|Azure Account Shared Access Signature (SAS)||Storage Account Name||SAS Token|
|Google Cloud Storage (GCS)||Access Key||Secure Email and Secret Access Key|
|Public access object stores||<empty string>
Enclose the empty string in single straight quotes: USER ''
Enclose the empty string in single straight quotes: PASSWORD ''
|Amazon S3 IAM||IAM is an alternative to using an access key and password to secure S3 buckets. To allow Advanced SQL Engine access to S3 buckets that use IAM, your S3 bucket policy must be configured with the following Actions for the role that allows access to the bucket:
|Azure Blob storage and Azure Data Lake Storage Gen2||A user with access key information has full control over the entire account. Alternatively, SAS can be defined on Containers, or on objects within containers, so it provides a more fine-grained authentication approach. NOS uses either type of authentication and does not need to know what type of secret is being supplied.
Only SAS tokens are supported. Service SAS tokens generate errors and are rejected.
|GCS||To allow Advanced SQL Engine access, the following permissions are needed:
See your cloud vendor documentation for instructions on creating an external object storage account.
- Create an external object store on a Teradata-supported external object storage platform. Give your external object store a unique name. In the Teradata-supplied examples, the bucket/container is called td-usgs. Because the external object store name must be unique, choose a name other than td-usgs.
- On Amazon, generate an access ID and matching secret key for your bucket or generate an Identity and Access Management (IAM) user credential. On Azure, generate SAS tokens (not Service SAS tokens) for your td-usgs container. On GCS, generate an access ID and matching secret key for your bucket.
- Download the sample data from https://downloads.teradata.com/ (look for NOS Download Data) to your client/laptop. The ZIP file contains sample river flow data in CSV, JSON, and Parquet data formats.
Copy the sample data to your bucket or container, being careful to preserve the data directory structure. For example, use a location similar to the following:
Note, you can use the Amazon S3 or Azure management consoles or a utility like AWS CLI to copy the data to your external object store. For GCS, you can use the gsutil tool to copy the data to your external object store.
- Amazon S3: /S3/YOUR-BUCKET.s3.amazonaws.com/JSONDATA
- Azure Blob storage and Azure Data Lake Storage Gen2: /az/YOUR-STORAGE-ACCOUNT.blob.core.windows.net/td-usgs/CSVDATA/
- GCS: /gs/storage.googleapis.com/YOUR-BUCKET/CSVDATA/
- In the example code replace the bucket or container (shown as td-usgs, YOUR-BUCKET, or YOUR-STORAGE-ACCOUNT) with the location of your object store.
- Replace YOUR-ACCESS-KEY-ID and YOUR-SECRET-ACCESS-KEY with the access values for your external object store.
The following steps may require the assistance of your public cloud administrator.