Skip to content
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

Adding emit_datasets param to DbtBaseOperator #551

Closed
wants to merge 2 commits into from

Conversation

pgoslatara
Copy link
Contributor

Description

When using the kubernetes execution mode I get this error:
image

This can be reproduced by following the README here, the relevant DAG file is here.

It appears that emit_datasets is not set in DbtBaseOperator, only in DbtLocalBaseOperator.

Related Issue(s)

Breaking Change?

Checklist

  • I have made corresponding changes to the documentation (if required)
  • I have added tests that prove my fix is effective or that my feature works

@pgoslatara pgoslatara requested a review from a team as a code owner September 25, 2023 18:39
@pgoslatara pgoslatara requested a review from a team September 25, 2023 18:39
@netlify
Copy link

netlify bot commented Sep 25, 2023

👷 Deploy Preview for amazing-pothos-a3bca0 processing.

Name Link
🔨 Latest commit cb82d82
🔍 Latest deploy log https://app.netlify.com/sites/amazing-pothos-a3bca0/deploys/6512d326762ab5000832b4c6

@pgoslatara pgoslatara temporarily deployed to external September 25, 2023 18:39 — with GitHub Actions Inactive
Copy link
Collaborator

@tatiana tatiana left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks a lot for the fix, @pgoslatara !

Would you be up for cherry-picking a test-case that covers this change so we avoid regression on this bug? I had created a test in 79f348b. If you'd rather not cherry-pick and create your own test, that would be fine as well!

@tatiana tatiana added this to the 1.1.2 milestone Sep 26, 2023
tatiana added a commit that referenced this pull request Sep 27, 2023
Fix behaviour when using `ExecutionMode.KUBERNETES`, broken between the
Cosmos releases 1.0.0 and 1.1.1.

Update the documentation to be representative of the 1.x Cosmos
interface:

https://astronomer.github.io/astronomer-cosmos/getting_started/kubernetes.html

Add unit tests to avoid regressions on these fixes.

Part of the documentation fixes are made in:
astronomer/cosmos-example#4

As a next step, we must ensure integration tests for running Cosmos on
K8s to avoid this breaking change moving forward (issue #535).

Closes: #493
Closes: #548
Closes: #534

Co-authored-by: Pádraic Slattery <[email protected]> (who created PR #551)
@tatiana
Copy link
Collaborator

tatiana commented Sep 27, 2023

Thanks a lot for working on this, @pgoslatara ! I've merged your change as part of #554, since it includes tests and a few more bits. You are credited as a co-author!

@tatiana tatiana closed this Sep 27, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants