Skip to content

Snowflake: Add EXTERNAL VOLUME DDL#2397

Draft
sabir-akhadov-localstack wants to merge 1 commit into
apache:mainfrom
localstack:pr/05-external-volume
Draft

Snowflake: Add EXTERNAL VOLUME DDL#2397
sabir-akhadov-localstack wants to merge 1 commit into
apache:mainfrom
localstack:pr/05-external-volume

Conversation

@sabir-akhadov-localstack

Copy link
Copy Markdown
Contributor

Snowflake's external-volume DDL did not parse. This adds CREATE [OR REPLACE] EXTERNAL VOLUME [IF NOT EXISTS], ALTER, DROP, DESCRIBE/DESC and SHOW EXTERNAL VOLUMES.

Example that failed before:

CREATE EXTERNAL VOLUME my_vol STORAGE_LOCATIONS = (
    (NAME = 'loc1' STORAGE_PROVIDER = 'S3' STORAGE_BASE_URL = 's3://bucket/path/'));

Within a storage location, STORAGE_BASE_URL, STORAGE_AWS_ROLE_ARN, STORAGE_AWS_EXTERNAL_ID and ENCRYPTION may appear in any order after NAME and STORAGE_PROVIDER, matching real Snowflake; the required STORAGE_BASE_URL and duplicate fields are validated after parsing. All statements round-trip.

See the Snowflake CREATE EXTERNAL VOLUME docs.

Snowflake's external-volume statements did not parse. This adds
CREATE [OR REPLACE] EXTERNAL VOLUME [IF NOT EXISTS], ALTER, DROP,
DESCRIBE/DESC and SHOW EXTERNAL VOLUMES.

Example that failed before:

    CREATE EXTERNAL VOLUME my_vol STORAGE_LOCATIONS = (
        (NAME = 'loc1' STORAGE_PROVIDER = 'S3'
         STORAGE_BASE_URL = 's3://bucket/path/'))

Storage locations accept STORAGE_BASE_URL, STORAGE_AWS_ROLE_ARN,
STORAGE_AWS_EXTERNAL_ID and ENCRYPTION in any order after NAME and
STORAGE_PROVIDER, matching real Snowflake; required fields and
duplicates are validated after parsing. All statements round-trip.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant