dbt: Propagate the dbt return code also when no OpenLineage events are emitted #2591
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.
Problem
This is a
missed corner casefollow-up of #2560dbt-ol
should always propagate dbt's return code, even when the script encounters an early exit because no lineage events were processed.Closes: #2558
Solution
Added
return return_code
to the early exit statements.One-line summary:
dbt-ol should propagate the exit code of the underlying dbt process even if no lineage events are emitted.
Checklist
SPDX-License-Identifier: Apache-2.0
Copyright 2018-2023 contributors to the OpenLineage project