Fokko commented on issue #3596: [AIRFLOW-2747] Explicit re-schedule of sensors
URL:
https://github.com/apache/incubator-airflow/pull/3596#issuecomment-448993725
I fully agree, @seelmann. My suggestion was to make it default for Airflow
2.0
Fokko commented on issue #3596: [AIRFLOW-2747] Explicit re-schedule of sensors
URL:
https://github.com/apache/incubator-airflow/pull/3596#issuecomment-447619213
@ashb @seelmann To simplify things, I'm all in for setting the re-schedule
method as the default scheduling method for sensors,
Fokko commented on issue #3596: [AIRFLOW-2747] Explicit re-schedule of sensors
URL:
https://github.com/apache/incubator-airflow/pull/3596#issuecomment-424346644
@mistercrunch PTAL, you can shut down some idling (or should I say poking)
machines now ;)
Fokko commented on issue #3596: [AIRFLOW-2747] Explicit re-schedule of sensors
URL:
https://github.com/apache/incubator-airflow/pull/3596#issuecomment-416023234
@seelmann I think this might have to do with a new release of Boto3:
https://pypi.org/project/boto3/#history
Fokko commented on issue #3596: [AIRFLOW-2747] Explicit re-schedule of sensors
URL:
https://github.com/apache/incubator-airflow/pull/3596#issuecomment-415710523
Maybe we could even make the rescheduling default behaviour for Airflow 2.0,
and get rid of the blocking tasks. That would also
Fokko commented on issue #3596: [AIRFLOW-2747] Explicit re-schedule of sensors
URL:
https://github.com/apache/incubator-airflow/pull/3596#issuecomment-415709674
@seelmann Can you base onto master?
This is an automated
