feat(entities) Adds batch entity and batch sql schema#46
Merged
Conversation
sbalabanov
requested changes
Feb 23, 2026
| // Request IDs will always be part of the same queue. | ||
| // For e.g. - [queueA/1, queueA/2, queueA/3]. | ||
| Contains []string | ||
| // Dependencies is a list of batch IDs (and associated metdata) for this batch. |
| Contains []string | ||
| // Dependencies is a list of batch IDs (and associated metdata) for this batch. | ||
| // Dependencies will always be part of the same queue. | ||
| Dependencies []map[string]interface{} |
Contributor
There was a problem hiding this comment.
may be need a more thorough explanation what deps are
| // Dependencies will always be part of the same queue. | ||
| Dependencies []map[string]interface{} | ||
| // The state of the batch lifecycle this batch is in. | ||
| State string |
Contributor
There was a problem hiding this comment.
prefer to type it explicitly off string type
| dependencies JSON NOT NULL, | ||
| state VARCHAR(255) NOT NUll, | ||
| version INT NOT NULL, | ||
| PRIMARY KEY (id,queue) |
8699556 to
b7d8ef7
Compare
This was referenced Feb 24, 2026
behinddwalls
approved these changes
Feb 24, 2026
b7d8ef7 to
48240ec
Compare
behinddwalls
added a commit
that referenced
this pull request
Feb 24, 2026
… it (#44) ## Summary feat(entities) Adds change provider entity and mysql backed store for it ## Why? <!-- Why is this change necessary? What is the motivation or justification? --> This sets up change provider entity and its corresponding sql store. This will be used by various workflows in the orchestrator to get information about changes going through the system. ## What? * Add a `ChangeProvider` entity * Add a `ChangeProviderStore` - the mysql store that backs this entity ## Test Plan ## Issues ## Stack 1. @ #44 1. #46 1. #47 1. #48 1. #49 --------- Co-authored-by: Preetam Dwivedi <behinddwalls@gmail.com>
manjari25
added a commit
that referenced
this pull request
Feb 24, 2026
## Summary feat(entities) Adds batch dependent entity and sql schema ## Why? <!-- Why is this change necessary? What is the motivation or justification? --> This sets up batch dependent entity and its corresponding sql schema. This helps make reverse look ups for batch dependencies easier throughout the system. ## What? * Add a `BatchDependent` entity * Add `batch_dependent` mysql schema * Note: `BatchDependentStore` in upcoming PR ## Test Plan ## Issues ## Stack 1. #44 1. #46 1. @ #47 1. #48 1. #49
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
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(entities) Adds batch entity and batch sql schema
Why?
This sets up batch entity and its corresponding sql schema. This establishes the core concept of a batch that will be used through the system.
What?
Batchentitybatchmysql schemaBatchStorein upcoming PRTest Plan
Issues
Stack