Hello Mishika,
I think we had the same use case in which we wanted an operator to use the
xcom values pushed from a previous try (after a retry) and also found out
that it is cleared before an execution. What we did is to extend Airflow
data model to hold the data we wanted to persist between
tion for us.
> Somesh
>
> -Original Message-
> From: Emmanuel Brard [mailto:emmanuel.br...@getyourguide.com]
> Sent: Friday, August 24, 2018 6:48 AM
> To: dev@airflow.incubator.apache.org
> Subject: Re: airflow 1.9 tasks randomly failing | k8 - hive
>
> Hey,
>
>
Hey,
We have a similar setup with Airflow 1.9 on Kubernetes with the Celery
executor.
We saw some airflow tasks being killed inside the container because of
cgroup limits (set by kubernetes and pushed to the docker daemon) but not
airflow itself (airflow celery command) which ended up in zombie
Hi everyone,
I've recently looked at the implementation of the ExternalTaskSensor sensor
and I was wondering if it would be a good idea to actually implement this
check (these checks) at the scheduler level. Basically the
ExternalTaskSensor runs a query against the backend database at regular
; Our team has a fix for it. I will get them to put it over into the
> airflow repo.
>
> Can you provide a specific example where your item is failing and I will
> make sure it gets included.
>
> Thanks,
> Mike
>
>
>
> > On Jun 19, 2018, at 10:57 AM, Emmanuel Brard <
&g
Hi,
When exporting variables, it looks like the export helper serialize to JSON
with JSON type, so an float is a float in the resulting file.
But then when importing from this file, there is no type convertion and
this step in the set_val method (class Variable) fails:
self._val =
