Adds /batch/ endpoint for batch processing api requests#807
Open
djperrefort wants to merge 18 commits intomainfrom
Open
Adds /batch/ endpoint for batch processing api requests#807djperrefort wants to merge 18 commits intomainfrom
djperrefort wants to merge 18 commits intomainfrom
Conversation
![github-advanced-security[bot]](https://avatars.githubusercontent.com/in/57789?s=60&v=4){kind=small}
djperrefort
changed the title
|
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
This PR introduces the batch app, a new endpoint allowing clients to submit multiple API requests as a single atomic job.
Rather than issuing requests individually and handling partial failures in client code, consumers can group related operations into an ordered sequence of steps executed within a single database transaction. If any step fails, the entire transaction is rolled back. Steps can also reference the response body of previous steps using
@ref{alias.dotpath}tokens, allowing the output of one request (e.g. a newly created record's ID) to be forwarded as input to the next. An optionaldry_runmode executes all steps without persisting any changes, allowing users to validate a job before committing it.