source-zendesk-support: checkpoint TicketMetricEvents state after every 1000 documents
#2014
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…very 1000 documents Previously, `TicketMetricEvents` was only emitting documents and checkpointing state after reading all available documents from Zendesk Support. `TicketMetricEvents` can take multiple hours to backfill, and any task restarts during the backfill caused `TicketMetricEvents` to start over completely instead of picking back up where it left off before the restart. Setting `state_checkpoint_interval` tells `TickeMetricEvents` to checkpoint state & emit documents after every 1000 documents and allows the stream to pick up where it left off if it's interrupted during a backfill.
Alex-Bair
added
the
change:unplanned
Alex-Bair
deleted the
bair/zendesk-support-ticketmetricevents-state-checkpoint
branch
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description:
Previously,
TicketMetricEventswas only emitting documents and checkpointing state after reading all available documents from Zendesk Support & getting caught up to the present.TicketMetricEventscan take multiple hours to backfill, and any task restarts during the backfill causeTicketMetricEventsto start over completely instead of picking back up where it left off before the restart.Setting
state_checkpoint_intervaltellsTickeMetricEventsto checkpoint state & emit documents after every 1000 documents, and this allows the stream to pick up where it left off if it's interrupted during a backfill.Workflow steps:
(How does one use this feature, and how has it changed)
Documentation links affected:
(list any documentation links that you created, or existing ones that you've identified as needing updates, along with a brief description)
Notes for reviewers:
Tested on a local stack. Confirmed that
TicketMetricEventscheckpoints state after every 1000 documents and uses the most recently checkpointed state if it's interrupted during a sweep/backfill.This change is