Fokko commented on issue #6370: AIRFLOW-5701: Don't clear xcom explicitly before execution URL: https://github.com/apache/airflow/pull/6370#issuecomment-546707884 First of all, you should be able to just serialize the execution_date. Instead of converting it to a string, and parse it again. I don't think your example is complete. What would be the value of the `execution_date` for each of the runs? There are two options: - They are the same. So on the first run, the `old_xcom` will be None, because it never ran before, and it will raise the error. On the second run, they will be equal, so the exception will not be raise. Same for the third run. - They are monotonically increasing. For example, a daily run. Then the first run will still error, and the second run will error as well since the first xcom will be smaller than the second. Bolke triggered me, in combination with your comment about the use of `include_prior_dates`. When you set this option to `True`, which is `False` by default, then the `xcom_pull` won't be idempotent anymore for the same taskinstance. Which it definitly should. So I'm thinking of making this configurable. By adding an option to the `xcom_pull`, for example, `include_self` (working name), which implies that it will also include earlier xcom's of itself.
---------------------------------------------------------------- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
