feat: dbt microbatch ref filter support#5292
Merged
Conversation
f7c5e95 to
c52d415
Compare
eakmanrq
commented
Sep 3, 2025
sqlmesh/core/renderer.py
Outdated
| ) | ||
| for ref in all_refs: | ||
| if ref.event_time_filter: | ||
| ref.event_time_filter["start"] = render_kwargs["start_tstz"] |
Collaborator
Author
There was a problem hiding this comment.
I use tstz since my testing with Postgres showed that dbt rendered a tstz. It might end up being adapter specific so this could change after more testing.
71295e5 to
6e137a4
Compare
erindru
approved these changes
Sep 8, 2025
6e137a4 to
1929b4f
Compare
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.
One behavior difference between dbt microbatch and SQLMesh incremental by time range is that dbt microbatch, by default, includes the date filter for you. You can opt-out of this by adding a
.render()after the ref. This PR adds that functionality.Some tricky parts of this:
EventTimeFilterhappens in two stages on SQLMesh - one when we load to record the event column and then at execution we add the start/endBETWEENin the expression. Therefore the end is made exclusive. An alternative approach is to patch the filter render method to have it use between which you can see that implementation in this commit: a595791