[
https://issues.apache.org/jira/browse/AIRFLOW-1135?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16789246#comment-16789246
]
jack commented on AIRFLOW-1135:
-------------------------------
[~ultrabug] what i'm trying to understand is for example how XCOM is different
from SLA miss in this context ?
Do you see value in keeping the DAG run data in tables: job, dag_run,
task_instance, sla_miss but allow deleting from xcom table?
To the best of my understanding the xcom table is a log like. hence there is no
reason to delete it unless you wish to remove all history of that dag run?
> Clearing XCom data from previous executions
> -------------------------------------------
>
> Key: AIRFLOW-1135
> URL: https://issues.apache.org/jira/browse/AIRFLOW-1135
> Project: Apache Airflow
> Issue Type: New Feature
> Components: db
> Reporter: Ultrabug
> Priority: Major
>
> It looks like XCom data from previous executions of tasks are never cleared
> from database and that there's no easy way to do so.
> Since XComs are created by execution_date of a task, when a task heavily uses
> XComs (like 20 000+) we can end up with a large xcom table on the database.
> Is there something I'm missing about cleaning up those previous XComs from
> database (since they're not used anymore) ?
> Would you accept the idea of having a new PR providing a helper to remove
> them ?
> Thanks
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
