feat(controller) Add batch ID generation via counter to batch controller#82
Merged
Conversation
manjari25
requested review from
a team,
behinddwalls and
sbalabanov
as code owners
sbalabanov
approved these changes
Feb 25, 2026
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
3 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.
Summary
feat(controller) Add batch ID generation via counter to batch controller
What?
The batch controller generates a unique batch ID using the counter.Counter extension (backed by MySQL). Each batch gets an ID in the format {queue}/batch/{seq} and a Batch entity is constructed from the request. Note that for now each batch maps to a single request. This will evolve in the future to have multiple requests map to a single batch with some conflict graph processing.
Why?
This wires in the counter extension to produce monotonically increasing, globally unique batch IDs per queue — a prerequisite for persisting batches and tracking their dependencies in future work.
Test Plan
Issues
#80