-
Notifications
You must be signed in to change notification settings - Fork 183
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
DbtTaskGroup - Kubernetes Execution with RenderConfig #943
Comments
It sounds like you're encountering an issue where using To address this, ensure that your Additionally, check for any recent changes or updates in the Cosmos repository that might affect this functionality. Specifically, look into the changelog for updates related to Docker and Kubernetes operators, as these could impact how If the issue persists, examining the logs or error messages for any clues on why the Kubernetes pod is not being initiated could provide further insights. The If you can provide more details about your configuration and any specific error messages you're encountering, it would help in diagnosing and resolving the issue more effectively.
|
@harshag7dm please, could you confirm which version of Cosmos you've tried, with which DAG? |
To try to reproduce this:
|
I investigated further and found that when the manifest is unavailable and the execution mode isn't set to ExecutionMode.LOCAL, we're using the custom parser to load the dbt project. However, this custom parser currently does not support selectors. astronomer-cosmos/cosmos/dbt/graph.py Lines 323 to 329 in 2994dba
The workaround I tried
In both cases, the DAG rendering is like below for dag https://github.com/astronomer/cosmos-example/blob/main/dags/jaffle_shop_kubernetes.py with addition param render_config render_config=RenderConfig(
select=["tag:customers"],
), |
…1101) The `load_via_custom_parser` method is not very effective when it comes to filtering. Currently, if the ExecutionMode is not Local, we always use load_via_custom_parser to parse the dbt project. However, I believe it's beneficial to utilize DBT LS whenever it's available. This PR removes the check if the execution mode is ExecutionMode.LOCAL before `load_via_dbt_ls` Related: #943
When I use Kubernetes Execution in DbtTaskGroup and try to filter out the Models using tag, it doesn't work. There is no Kubernetes pod being run.
If I remove the RenderConfig, then all the models are run?
Is this a bug or am I missing something?
The text was updated successfully, but these errors were encountered: