Agreed. This is a bug and imho a blocker for 1.8.1.
My bad: re-implementation and lack of sufficient unit tests is what is causing
this.
I'll have a look at this asap.
Bolke.
Sent from my iPhone
> On 19 Apr 2017, at 02:52, Maxime Beauchemin
> wrote:
>
> @Chris this is not the way backf
-1.
Not sure if these have been called out earlier.
For all the bundled files with different licenses (MIT, BSD, etc), the full
texts of these licenses should be in the source tarball preferably at the
end of the LICENSE file.
webgl-2d needs to be called out as MIT license.
Version in pkg-info ha
@Chris this is not the way backfill was designed originally and to me
personally I'd flag the behavior you describe as a bug.
To me, backfill should just "fill in the holes", whether the state came
from a previous backfill run, or the scheduler.
`airflow backfill` was originally designed to be us
Another approach :
1. Airflow calls webservice in a fire-and-forget fashion
2. Webservice updates a message bus/stream (e.g. SQS) with result
3. An airfllow sensor pulls updates off SQS and processes them
This saves airflow from polling your webservice which would in turn poll
your DB. Additionall
I asked a very similar question last month and got no responses. Note that
SubDags execute backfill commands in in 1.8.0. The original text of that
question is as follows:
I've recently upgraded to 1.8.0 and immediately encountered the hanging
SubDag issue that's been mentioned. I'm not sure the r
Hi all,
I'm new to Airflow, and I'm looking for someone to clarify the expected
behavior of running a backfill with regard to previously successful
tasks. When I run a backfill on 1.8.0, tasks that were previously run
successfully are re-run for me. Is it expected that backfills re-run all
tasks
The proper way to do this is for your service to return a token (unique
identifier for the long running process) asynchronously (immediately), and
to then call another endpoint to check on the status while passing this
token.
Since this is Airflow and you have the luxury of having a lot of predefi
Hi All,
We have a use case where we are building Airflow DAG consisting of few
tasks and each task (HttpOperator) is calling the service running behind
AWS Elastic Load Balancer (ELB).
Since these tasks are the long running process so I'm getting 504 GATEWAY
TIMEOUT HTTP status code and resulting
https://issues.apache.org/jira/browse/AIRFLOW-1121
Jira filed.
On Tue, Apr 18, 2017 at 1:27 PM, siddharth anand wrote:
> Sure. As soon as I get out of my meetings.
>
> -s
>
> On Tue, Apr 18, 2017 at 1:01 PM Chris Riccomini
> wrote:
>
>> @Sid, can you open JIRA(s), and assign them as blockers t
Sure. As soon as I get out of my meetings.
-s
On Tue, Apr 18, 2017 at 1:01 PM Chris Riccomini
wrote:
> @Sid, can you open JIRA(s), and assign them as blockers to 1.8.1?
>
> On Tue, Apr 18, 2017 at 12:39 PM, siddharth anand
> wrote:
>
> > I've run into a regression with the webserver. It looks
@Sid, can you open JIRA(s), and assign them as blockers to 1.8.1?
On Tue, Apr 18, 2017 at 12:39 PM, siddharth anand wrote:
> I've run into a regression with the webserver. It looks like the --pid
> argument is no longer honored in 1.8.1. The pid file is not being written
> out! As a result, moni
I've run into a regression with the webserver. It looks like the --pid
argument is no longer honored in 1.8.1. The pid file is not being written
out! As a result, monitd, which watches the processes mentioned in the pid
file, keep trying to spawn webservers.
HISTTIMEFORMAT="%d/%m/%y %T "
PYTHONPAT
Hmn.. it always worked for me for any of the releases we installed. I
install `pip install `
-s
On Tue, Apr 18, 2017 at 10:44 AM, Chris Riccomini
wrote:
> @Sid, how do you enable the versioning? I've never been able to get this to
> work in my environment. It always shows "Not available", even
@Sid, how do you enable the versioning? I've never been able to get this to
work in my environment. It always shows "Not available", even with 1.8.0.
On Mon, Apr 17, 2017 at 11:18 PM, Bolke de Bruin wrote:
> Hey Alex,
>
> I agree with you that they are nice to have, but as you mentioned they are
14 matches
Mail list logo
