When a Pipe is recreated using the CREATE OR REPLACE PIPE command:
When a Pipe is recreated using the CREATE OR REPLACE PIPE command:
When the CREATE OR REPLACE PIPE command is used to recreate a pipe in Snowflake, the load history of the pipe is reset to empty. This means that the metadata of the pipe, which contains records of previously processed files, is cleared. This action can potentially result in the reloading of files if there are no other mechanisms in place to prevent it. The REFRESH parameter is not automatically set to TRUE upon recreating a pipe, and there are no inherent mechanisms to ignore previously loaded files as suggested in other options.
I believe the correct answer is A. REFRESH is a parameter for ALTER PIPE https://docs.snowflake.com/en/sql-reference/sql/alter-pipe.html It is NOT a parameter for CREATE [OR REPLACE] Pipe. https://docs.snowflake.com/en/sql-reference/sql/create-pipe.html Further recreating a pipe resets history: https://docs.snowflake.com/en/user-guide/data-load-snowpipe-manage.html#label-snowpipe-management-recreate-pipes "Load History The load history for Snowpipe operations is stored in the metadata of the pipe object. When a pipe is recreated, the load history is dropped. In general, this condition only affects users if they subsequently execute an ALTER PIPE … REFRESH statement on the pipe. Doing so could load duplicate data from staged files in the storage location for the pipe if the data was already loaded successfully and the files were not deleted subsequently."
a is correct
A is the correct ans. Load History The load history for Snowpipe operations is stored in the metadata of the pipe object. When a pipe is recreated, the load history is dropped. In general, this condition only affects users if they subsequently execute an ALTER PIPE … REFRESH statement on the pipe. Doing so could load duplicate data from staged files in the storage location for the pipe if the data was already loaded successfully and the files were not deleted subsequently.
REFRESH is a parameter for ALTER PIPE
correct answer: A
A Is correct Answer
Correct answer:A
A. The Pipe load history is reset to empty When you recreate a pipe using CREATE OR REPLACE PIPE, the load history for the pipe is reset, which means Snowflake will no longer have a record of the files that were previously processed by that pipe. This can affect how subsequent loads are handled, but the REFRESH parameter and handling of previously loaded files are not automatically impacted in the ways described by options B and C.
The correct answer is A https://docs.snowflake.com/en/user-guide/data-load-snowpipe-manage
Answer is A. Ref: https://docs.snowflake.com/en/user-guide/data-load-snowpipe-manage
D When a Pipe is recreated using the CREATE OR REPLACE PIPE command, the load history is reset, the REFRESH parameter is set to TRUE, and previously loaded files are ignored.
D is correct Recreating Pipes - Load History:(As per documentation) The load history for Snowpipe operations is stored in the metadata of the pipe object. When a pipe is recreated, the load history is dropped. In general, this condition only affects users if they subsequently execute an ALTER PIPE … REFRESH statement on the pipe. Doing so could load duplicate data from staged files in the storage location for the pipe if the data was already loaded successfully and the files were not deleted subsequently. https://docs.snowflake.com/en/user-guide/data-load-snowpipe-manage#label-snowpipe-management-recreate-pipes
correct option is A https://docs.snowflake.com/en/user-guide/data-load-snowpipe-manage check load history topic
B is the answer
B is correct
A is correct. The load history for Snowpipe operations is stored in the metadata of the pipe object. When a pipe is recreated, the load history is dropped. In general, this condition only affects users if they subsequently execute an ALTER PIPE … REFRESH statement on the pipe. Doing so could load duplicate data from staged files in the storage location for the pipe if the data was already loaded successfully and the files were not deleted subsequently. https://docs.snowflake.com/en/user-guide/data-load-snowpipe-manage.html#recreating-pipes
A is correct