Answer is C & D.
Not B as:
https://docs.snowflake.com/en/sql-reference/sql/create-pipe.html#usage-notes
All COPY INTO <table> copy options are supported except for the following:
FILES = ( 'file_name1' [ , 'file_name2', ... ] )
ON_ERROR = ABORT_STATEMENT
SIZE_LIMIT = num
PURGE = TRUE | FALSE (i.e. automatic purging while loading)
FORCE = TRUE | FALSE
The correct options for what is true of Snowpipe via REST API are:
C. Snowflake automatically manages the compute required to execute the Pipe's COPY INTO commands
D. Snowpipe keeps track of which files it has loaded
Here's why the other options are not accurate:
A. You can only use it on Internal Stages: You can use Snowpipe via REST API with both Internal Stages (located within Snowflake storage) and External Stages (referencing data in external cloud storage providers like S3 or Azure Blob Storage).
B. All COPY INTO options are available during pipe creation: Not all COPY INTO options are available through the Snowpipe REST API for pipe creation. While the core functionality is supported, some advanced options might be limited through the API compared to directly using the COPY INTO command within Snowflake.
A voting comment increases the vote count for the chosen answer by one.
Upvoting a comment with a selected answer will also increase the vote count towards that answer by one.
So if you see a comment that you already agree with, you can upvote it instead of posting a new comment.
redsky0
Highly Voted 3 years, 4 months agoMallikharjuna452
Most Recent 10 months, 2 weeks ago372110c
11 months, 1 week agopranalig
11 months, 2 weeks agoPrashantGupta1616
12 months agoAlex_Ovidiu
1 year, 1 month agooscarglob
1 year, 7 months agoMayuri917233
2 years agoRajuNaik
2 years, 1 month agoPrajdeo
2 years, 2 months agoBigDataBB
2 years, 4 months agoTapasgup007
2 years, 5 months agobharathmv
2 years, 8 months agoDK69
3 years agoAGuru2020
3 years, 2 months agovivek_nitd
3 years, 3 months agoRajokkiyam
3 years, 3 months ago