-
Notifications
You must be signed in to change notification settings - Fork 14.6k
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
EMRServerlessStartJobOperator Expand/Expand Kwargs not Serializing properly #38005
Comments
Thanks for opening your first issue here! Be sure to follow the issue template! If you are willing to raise PR to address this issue please do so, no need to wait for approval. |
I will be working on this. Full stack trace for reference: [2024-03-09T00:45:58.280+0000] {logging_mixin.py:188} INFO - [2024-03-09T00:45:58.280+0000] {dagbag.py:540} INFO - Filling up the DagBag from /files/dags/example_mapped_emr_serverless.py During handling of the above exception, another exception occurred: Traceback (most recent call last): |
Apache Airflow Provider(s)
amazon
Versions of Apache Airflow Providers
apache-airflow-providers-amazon==8.19.0
Apache Airflow version
2.8.2
Operating System
Debian GNU/Linux 12 (bookworm)
Deployment
Docker-Compose
Deployment details
Used breeze tool to deploy.
What happened
When using the
EmrServerlessStartJobOperator
, using the airflow expand functionality is not possible. The DAG will fail to serialize and it shows a DAG import error in the webserver. This is becauseEmrServerlessStartJobOperator.operator_extra_links
is called andEmrServerlessStartJobOperator
is of typeMappedOperator
, butMappedOperator
does not have theEmrServerlessStartJobOperator.is_monitoring_in_job_override
attribute.What you think should happen instead
DAG should import successfully without any errors.
How to reproduce
The following single usage of EmrServerlessStartJobOperator works:
Whereas the following usage of expanded EmrServerlessStartJobOperator will fail to serialize:
Anything else
No response
Are you willing to submit PR?
Code of Conduct
The text was updated successfully, but these errors were encountered: