XCom delete in ui and db clean do not trigger delete for custom backend #31774
Labels
affected_version:main_branch
Issues Reported for main branch
area:UI
Related to UI/UX. For Frontend Developers.
kind:bug
This is a clearly a bug
Apache Airflow version
Other Airflow 2 version (please specify below)
What happened
When using the delete button in the UI or running the airflow db clean on the XCom table the delete method does not seem to get triggered for a custom backend.
What you think should happen instead
Expect the delete method to be called so the custom backend can remove the linked file.
How to reproduce
Using this custom backend
The delete method never seems to be called. The clear method works as i can see the XCom disappear and reappear.
Operating System
Linux 9e28031d19f0 5.15.49-linuxkit #1 SMP PREEMPT Tue Sep 13 07:51:32 UTC 2022 x86_64 GNU/Linux
Versions of Apache Airflow Providers
apache-airflow 2.5.3
apache-airflow-providers-amazon 8.0.0
apache-airflow-providers-asana 2.1.0
apache-airflow-providers-celery 3.1.0
apache-airflow-providers-cncf-kubernetes 6.1.0
apache-airflow-providers-common-sql 1.4.0
apache-airflow-providers-databricks 4.1.0
apache-airflow-providers-ftp 3.3.1
apache-airflow-providers-google 10.0.0
apache-airflow-providers-http 4.3.0
apache-airflow-providers-imap 3.1.1
apache-airflow-providers-jdbc 3.3.0
apache-airflow-providers-mysql 5.0.0
apache-airflow-providers-postgres 5.4.0
apache-airflow-providers-redis 3.1.0
apache-airflow-providers-salesforce 5.3.0
apache-airflow-providers-slack 7.2.0
apache-airflow-providers-snowflake 4.0.5
apache-airflow-providers-sqlite 3.3.2
apache-airflow-providers-ssh 3.6.0
google-cloud-orchestration-airflow 1.4.1
Deployment
Official Apache Airflow Helm Chart
Deployment details
I'm testing this in Docker using a custom image that we deploy onto a Kubernetes cluster. It is designed to store the XComs on an efs volume attached to it. Locally in docker, the location is a mapped volume onto my local HD so I can see the files.
Anything else
every time
Are you willing to submit PR?
Code of Conduct
The text was updated successfully, but these errors were encountered: