ExamGecko
Question list
Search
Search

List of questions

Search

Question 89 - DEA-C01 discussion

Report
Export

Dominic, a Data Engineer wants to resume the pipe named stalepipe3 which got stale after 14 days.

To do the same, he called the SYSTEM$PIPE_FORCE_RESUME function select system$ pipe_force_resume('snowmydb.mysnowschema.stalepipe3','staleness_check_override');

Let's say If the pipe is resumed 16 days after it was paused, what will happened to the event notification that were received on the first and second days after the pipe was paused?

A.
Snowpipe generally skips any event notifications that were received on the first and second days after the pipe was paused.
Answers
A.
Snowpipe generally skips any event notifications that were received on the first and second days after the pipe was paused.
B.
Pipe maintains Metadata history of files for 64 days, so in this scenarios Snowpipe pro-cessed all the event notifications that were received for 16 days or so.
Answers
B.
Pipe maintains Metadata history of files for 64 days, so in this scenarios Snowpipe pro-cessed all the event notifications that were received for 16 days or so.
C.
Once the Pipe got stale, all the events got purged automatically & pipe needs to be rec-reated with modified properties.
Answers
C.
Once the Pipe got stale, all the events got purged automatically & pipe needs to be rec-reated with modified properties.
D.
All the events get processed from day 1 if the PURGE properties in the PIPE object definition set to be FALSE initially.
Answers
D.
All the events get processed from day 1 if the PURGE properties in the PIPE object definition set to be FALSE initially.
Suggested answer: A

Explanation:

When a pipe is paused, event messages received for the pipe enter a limited retention period. The period is 14 days by default. If a pipe is paused for longer than 14 days, it is considered stale.

To resume a stale pipe, a qualified role must call the SYSTEM$PIPE_FORCE_RESUME function and input the STALENESS_CHECK_OVERRIDE argument. This argument indicates an under-standing that the role is resuming a stale pipe.

For example, resume the stale stalepipe1 pipe in the mydb.myschema database and schema:

select sys-tem$pipe_force_resume('mydb.myschema.stalepipe3','staleness_check_override');

As an event notification received while a pipe is paused reaches the end of the limited retention period, Snowflake schedules it to be dropped from the internal metadata. If the pipe is later resumed,

Snowpipe processes these older notifications on a best effort basis. Snowflake cannot guarantee that they are processed.

For example, if a pipe is resumed 15 days after it was paused, Snowpipe generally skips any event notifications that were received on the first day the pipe was paused (i.e. that are now more than 14 days old). If the pipe is resumed 16 days after it was paused, Snowpipe generally skips any event notifications that were received on the first and second days after the pipe was paused. And so on.

asked 23/09/2024
luis gilberto correa betancur
44 questions
User
Your answer:
0 comments
Sorted by

Leave a comment first