dbt, openlineage: set run_id after defer, do not log error if operator has no run_id set - #34270
Merged
Merged
Conversation
…r has no run_id set Signed-off-by: Maciej Obuchowski <obuchowski.maciej@gmail.com>
eladkal
approved these changes
Sep 11, 2023
potiuk
approved these changes
Sep 11, 2023
Member
|
(pending fixing tests :) ) |
Signed-off-by: Maciej Obuchowski <obuchowski.maciej@gmail.com>
6 tasks
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.
In the original PR, the OpenLineage implementation required having
self.run_idattribute being set up onDbtCloudRunJobOperator. This was not the case if the operator was used in deferrable mode.In this PR, we both set this attribute on
execute_complete, and defensively check for it in OpenLineage method implementation.