DESCRIBE PIPE¶
Describes the properties specified for a pipe, as well as the default values of the properties.
DESCRIBE can be abbreviated to DESC.
- See also:
Syntax¶
DESC[RIBE] PIPE <name>
Parameters¶
name
Specifies the identifier for the pipe to describe. If the identifier contains spaces or special characters, the entire string must be enclosed in double quotes. Identifiers enclosed in double quotes are also case-sensitive.
Usage notes¶
Returns results only for the pipe owner (i.e. the role with the OWNERSHIP privilege on the pipe), a role with the MONITOR or OPERATE privilege on the pipe, or a role with the global MONITOR EXECUTION privilege.
To determine the current status of a pipe, query the SYSTEM$PIPE_STATUS function.
To post-process the output of this command, you can use the RESULT_SCAN function, which treats the output as a table that can be queried.
Output¶
The command output provides pipe properties and metadata in the following columns:
| created_on | name | database_name | schema_name | definition | owner | notification_channel | comment | integration | pattern | error_integration | invalid_reason | kind |
Column |
Description |
---|---|
|
Date and time when the pipe was created. |
|
Name of the pipe. |
|
Database in which the pipe is stored. |
|
Schema in which the pipe is stored. |
|
COPY statement used to load data from queued files into a Snowflake table. |
|
Name of the role that owns the pipe (i.e. that has the OWNERSHIP privilege on the pipe). |
|
Amazon Resource Name of the Amazon SQS queue for the stage named in the DEFINITION column. |
|
Comment for this pipe. |
|
Name of the notification integration for pipes that rely on notification events to trigger data loads from Google Cloud Storage or Microsoft Azure cloud storage. |
|
PATTERN copy option value in the COPY INTO <table> statement in the pipe definition, if the copy option was specified. |
|
Notification integration name for pipes that rely on error events in Amazon S3 cloud storage to trigger notifications. |
|
Displays some detailed information for your pipes that may have issues. You can use the provided information to troubleshoot your pipes more effectively along with SYSTEM$PIPE_STATUS. If there is no issue with the pipe, the value is NULL. |
|
The kind of the pipe, either KAFKA or STAGE. |
Kafka-related columns
Column |
Description |
---|---|
|
Name of the external access integration used with Kafka. |
|
Name of the secret used with Kafka. |
|
Row format of records: |
|
Schema of records represented as variant. |
|
Name of a synchronized topic. |
Examples¶
Describe the mypipe
pipe created in the examples in CREATE PIPE:
desc pipe mypipe; +-------------------------------+--------+---------------+-------------+---------------------------------+----------+---------+ | created_on | name | database_name | schema_name | definition | owner | comment | |-------------------------------+--------+---------------+-------------+---------------------------------+----------+---------| | 2017-08-15 06:11:05.703 -0700 | MYPIPE | MYDATABASE | PUBLIC | copy into mytable from @mystage | SYSADMIN | | +-------------------------------+--------+---------------+-------------+---------------------------------+----------+---------+