-
Notifications
You must be signed in to change notification settings - Fork 294
Fix watcher fallback selector for versioned dbt models #2659
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
+16
−2
Merged
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@pankajkoti, maybe instead of hard-coding index 2, we could retrieve the last index, similar to what we were doing:
Do we have any official docs on how dbt forms
model_unique_id? It could be worth mentioning what the variations are, that normally there would be two dots, but in some cases there are more, and why it is safe to group the last dotsThere was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
On
[2]vs[-1]: I'd lean toward keeping[2]. For a well-formedunique_id, they return the same value; the difference is the failure mode.[2]raisesIndexErrorand surfaces malformed input loudly, while[-1]would silently fall back to thepackageorresource_typeand mis-issue the dbt command. It also matches the canonical parse already used inDbtNode.resource_name(cosmos/dbt/graph.py) and in cosmos/operators/watcher.py at lines 340, 546, and 613.On the docs ask: per the dbt manifest spec, node unique_ids are
<resource_type>.<package>.<resource_name>. Bothresource_typeandpackageare constrained identifiers that cannot contain dots, so the first two dots are unambiguous separators and everything after the second dot is the full resource name. For versioned models, dbt appends a fourth segment:model.<package>.<resource_name>.<version>(see node_args.py).split(".", 2)[2]returns the whole remainder (my_model.v1);split(".")[-1]returns justv1, which is the bug this PR fixes as mentioned in the PR description.I would like to skip adding an inline docstring at this site because the parse is open-coded in multiple places across the codebase that are linked above.
As we agreed, I am following up with a refactor PR that reuses a common method for these sites.