Re: schedule backfill jobs in reverse order

Nothing I know of. The scheduler finds the latest execution then creates the next based off interval; this is also why update to start date have no affect (doesn't try to fill gaps) On Mon, Apr 2, 2018, 11:26 AM Dennis O'Brien wrote: > Hi folks, > > I recently asked

Podling Report Reminder - April 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, 18 April 2018, 10:30 am PDT. The report for your podling will form

Re: DAG Level permissions (was Re: RBAC Update)

Hi everyone, Thanks a lot for all the great discussions. To summarize in brief, here are the few approaches we discussed so far: 1. One permission per DAG. The user has homogenous rights on the dag. The concerns: - not flexible to certain use cases(e.g the user has view only access on

schedule backfill jobs in reverse order

Hi folks, I recently asked this question on gitter but didn't get any feedback. Anyone know if there is a way to get the scheduler to reverse the order of the dag runs? By default a new DAG starts at start_date then moves sequentially forward in time until it is caught up (assuming

Re: RBAC Update

To my mind, I would expect the MVP of per-DAG RBAC to include three settings: viewing DAG state, executing or modifying DAGs, and viewing tasks within the DAG (logs/code/details). For instance we would love to expose a view of the production dataload state to our engineers, without exposing