Skip to content
This repository has been archived by the owner on Feb 9, 2024. It is now read-only.

ordered pipeline exec #64

Closed
wants to merge 1 commit into from
Closed

Conversation

dselans
Copy link
Contributor

@dselans dselans commented Jan 26, 2024

Changed to do ordered pipeline exec. Needed so that schema inference is always executed first - that way last step status can be put in resp. Without this, it is possible that schema inference pipeline gets executed first and so would cause the incorrect status set on the response.

Given that a lot of changes need to occur on the server - maybe there's a better way to do this.

Need to discuss with @blinktag

@dselans
Copy link
Contributor Author

dselans commented Jan 26, 2024

COPY/PASTE:

Arrived at the conclusion that we need to establish pipeline order on server. Without that, we will never be able to 100% say that X should execute before Y - at best, they are "it will probably happen".

Closing this PR in favor of the "pipeline refactor" PR.

@dselans dselans closed this Jan 26, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant