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

Document Failure Scenarios/behaviors #682

Open
uchennakevinm1 opened this issue Oct 18, 2022 · 0 comments
Open

Document Failure Scenarios/behaviors #682

uchennakevinm1 opened this issue Oct 18, 2022 · 0 comments
Labels
roadmap Planned for a future release
Milestone

Comments

@uchennakevinm1
Copy link
Contributor

uchennakevinm1 commented Oct 18, 2022

What happens to our message delivery and ordering guarantees during various failure scenarios.

Fixed number of failure scenarios:

  1. Upstream resource failure
  2. Connector Failure / Error - Bug in the connector code. Something about not typical operating behavior.
  3. Conduit
  4. Transforms
  5. Downstream Connector
  6. Downstream Resource

Make each one of these steps fail and then write down what the developer can expect.

Resist the urge to fix bad behaviors. We’ll prioritize that work appropriately.

At a minimum get the list of places where we need to test.

@uchennakevinm1 uchennakevinm1 added this to the 0.4.0 milestone Oct 18, 2022
@uchennakevinm1 uchennakevinm1 moved this to Triage in Conduit Main Oct 19, 2022
@lovromazgon lovromazgon moved this from Triage to Todo in Conduit Main Oct 21, 2022
@uchennakevinm1 uchennakevinm1 moved this from Todo to Triage in Conduit Main Jan 17, 2023
@uchennakevinm1 uchennakevinm1 modified the milestones: 0.4.0, Future Feb 1, 2023
@uchennakevinm1 uchennakevinm1 removed the status in Conduit Main Feb 13, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
roadmap Planned for a future release
Projects
Status: No status
Status: No status
Development

No branches or pull requests

1 participant