COPY FROM with Endpoint
Overview
When running COPY FROM queries, you should have the option to include the endpoint URL. This feature is especially useful for scenarios where you need to provide credentials and specific endpoints.
Syntax
The syntax is as follows:
AWS_CRED
with AZURE_CRED
or GCS_CRED
when copying from the Azure Blob Storage or Google Cloud Storage.Here’s the breakdown of syntax parameters:
-
Shared parameters:
table_name
: table that will receive data from the filefile_path
: link to the file location accessible from the server
-
Parameters in
AWS_CRED
:aws_region
: AWS region associated with the storage service (e.g. ‘region1’)key_id
: key identifier for authenticationaccess_key
: access key for authenticationendpoint_url
: URL endpoint for the storage service
-
Parameters in
GCS_CRED
:<path_to_credentials>
: path to JSON credentials file
-
Parameters in
AZURE_CRED
:tenant_id
: tenant identifier representing your organization’s identity in Azureclient_id
: client identifier used for authenticationclient_secret
: secret identifier acting as a password for authentication.
Examples
COPY FROM with AWS S3 Bucket
In this example, we are using the COPY FROM statement to import data from a file named students_file
and the endpoint is s3.us-east-2.amazonaws.com
.
Expected Output: Data from students_file
is copied into the students
table
COPY FROM with Google Cloud Storage
This example shows how to use the COPY FROM
statement to import data, but this time, the data is stored on Google Cloud Storage;
You can also copy the data using the AWS_CRED
like below, with the following endpoint https://storage.googleapis.com
.
Expected Output: Data from project_file
is copied into the project
table.
COPY FROM with Azure BlobStorage
It’s a similar story for getting the data from Azure Blob Storage.
Expected Output: Data from the your_blob
is copied into the taxi_data
.