fix: dbt microbatch parameter conversion#5298
Merged
Conversation
erindru
approved these changes
Sep 4, 2025
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.
Fixes two misunderstanding of the dbt microbatch:
batch_sizeis always 1 for dbt microbatch. In other words, they never issue a query that spans multiple intervals.concurrent_batchesreally determines, in SQLMesh terms, if a model depends on self which ultimately determine if the snapshot depends on past. Like SQLMesh, dbt determines this automatically by looking for self-referenes but users can force this with theconcurrent_batchesflag. Therefore if we see isFalse, meaning it should run sequentially, then we add the model to thedepends_on.