QuestionQ57

Ingest and Process Data

A Data Engineer is creating a pipe by running the following statement:

create or replace pipe mypipe auto_ingest=true as copy into mytable from @mystage;  

The Data Engineer adds a file named data.csv.gz to the stage, and it loads successfully into the mytable table.

What would cause data.csv.gz to be loaded a second time?

Choose two
Explanation

Snowpipe and a manually run COPY INTO <table> operation maintain separate load histories, so running COPY INTO mytable FROM @mystage can load a file previously ingested through Snowpipe. Snowpipe load history is stored in the pipe object; CREATE OR REPLACE PIPE recreates the pipe and removes that history. Running ALTER PIPE ... REFRESH afterward can queue the still-staged file for another load. Truncating the target table does not delete Snowpipe file-loading metadata.

Learn more

Community Discussion

No comments yet. Be the first to start the discussion!