Help with podling status report?

Hey all, If someone has an extra 15m today, could you please fill out: https://wiki.apache.org/incubator/February2018 Anyone is welcome to fill it out (via https://incubator.apache.org/guides/ppmc.html#podling_status_reports): > The PPMC does not have to fill out the report itself; the PPMC is

Podling Report Reminder - February 2018

Dear podling, This email was sent by an automated system on behalf of the Apache Incubator PMC. It is an initial reminder to give you plenty of time to prepare your quarterly board report. The board meeting is scheduled for Wed, 21 February 2018, 10:30 am PDT. The report for your podling will

Re: Rerunning task without cleaning DB?

Would rerunning a task be different from manually triggering that task? On Mon, Feb 5, 2018 at 4:09 PM, David Capwell wrote: > When a production issue happens it's common that we clear the history to > get airflow to run the task again. This is problematic since it throws >

Re: Rerunning task without cleaning DB?

We can't do that, unfortunately. Airflow schedule the task based on the current state in the DB. If you would like to preserve the history one option would be to add instrumentation on airflow_local_settings.py Regards, Ananth.P, On 5 February 2018 at 13:09, David Capwell

Re: Rerunning task without cleaning DB?

If you want to keep the rest of your history you can: 1. turn the DAG off 2. delete its bad tasks, delete the bad DAG run 3. turn the DAG on 4. let it backfill or hit the play button manually depending on your needs Unfortunately this does not keep the task you are working with, but it's better

Re: Rerunning task without cleaning DB?

Ananth, I am not familiar with that and couldn't find any reference in the code, can you say more? On Feb 7, 2018 3:02 PM, "Trent Robbins" wrote: > If you want to keep the rest of your history you can: > > 1. turn the DAG off > 2. delete its bad tasks, delete the bad DAG run