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

SparkKubernetes doesn't work with the "application_file" kwarg #38537

Closed
2 tasks done
eylonronen opened this issue Mar 27, 2024 · 1 comment
Closed
2 tasks done

SparkKubernetes doesn't work with the "application_file" kwarg #38537

eylonronen opened this issue Mar 27, 2024 · 1 comment
Labels
area:providers kind:bug This is a clearly a bug needs-triage label for new issues that we didn't triage yet

Comments

@eylonronen
Copy link

Apache Airflow Provider(s)

cncf-kubernetes

Versions of Apache Airflow Providers

apache-airflow-providers-cncf-kubernetes==8.0.0

Apache Airflow version

2.8.2

Operating System

Deployment

Official Apache Airflow Helm Chart

Deployment details

No response

What happened

When using the "application_file" kwarg and passing a yaml file path the operator fails because it tries to open a file that is not found.
The issue is that because application_file is a template_field and "yaml" is a template_ext, Airflow reads the yaml file, renders the jinja template and sets the attribute to be the content of the file, which then in "manage_template_specs" method the operator tries to open (that's the 2nd time) and fails

What you think should happen instead

passing a path to an application file using the application_file should work without failures

How to reproduce

Use the SparkKubernetesOperator with the application_file kwarg without failures

Anything else

No response

Are you willing to submit PR?

  • Yes I am willing to submit a PR!

Code of Conduct

@eylonronen eylonronen added area:providers kind:bug This is a clearly a bug needs-triage label for new issues that we didn't triage yet labels Mar 27, 2024
@Taragolis
Copy link
Contributor

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area:providers kind:bug This is a clearly a bug needs-triage label for new issues that we didn't triage yet
Projects
None yet
Development

No branches or pull requests

2 participants