Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Leech Pipeline - FAILURE status handling #58

Open
bradegler opened this issue May 16, 2023 · 0 comments
Open

Leech Pipeline - FAILURE status handling #58

bradegler opened this issue May 16, 2023 · 0 comments
Labels
enhancement New feature or request

Comments

@bradegler
Copy link
Contributor

TL;DR

Logs with a FAILURE status are currently filtered out of the query.

We need to figure out a way to mark how many attempts have been made for a particular delivery id preferably without causing an update to the row in BigQuery.

The simplest approach would be to just not write a FAILURE status and let the query try again.

The drawback is that something could be stuck forever in that situation and we wouldn't want to keep processing it. I think a secondary FAILURE table might work that we can join into the main query as WHERE count(failures where delivery_id = x) < 10 or something.

This adds complexity to the write operation though so it requires some thought.

Detailed design

No response

Alternatives considered

No response

Additional information

No response

@bradegler bradegler added the enhancement New feature or request label May 16, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Development

No branches or pull requests

1 participant