Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

BackfillJob overrides start date but that doesn't propagate to executor commands #1255

Closed
jlowin opened this issue Mar 29, 2016 · 1 comment
Assignees

Comments

@jlowin
Copy link
Member

jlowin commented Mar 29, 2016

I'm frankly not sure if this is a bug or not but it's weird so I'm creating a tracking issue for it. This will probably be addressed as part of either the #1225 resolution or the start_date roadmap item.

BackfillJob overrides the start date of a dag and its tasks. However, the override doesn't carry through to the executor commands. For example, SequentialExecutor issues an airflow run command and loads the same dag with its original start date.

This creates a problem because BackfillJob will always think the first iteration of a task with depends_on_past=True is runnable, since the execution date and start date match. But the executor it assigns to run that task will conclude that it it NOT runnable, because execution date and start date don't match.

@jlowin
Copy link
Member Author

jlowin commented Apr 3, 2016

Closed in #1271

@jlowin jlowin closed this as completed Apr 3, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant