[
https://issues.apache.org/jira/browse/AIRFLOW-2352?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Anonymous reassigned AIRFLOW-2352:
----------------------------------
Assignee: Alex Lumpov
> Airflow isn't picking up earlier periods after DAG definition update
> --------------------------------------------------------------------
>
> Key: AIRFLOW-2352
> URL: https://issues.apache.org/jira/browse/AIRFLOW-2352
> Project: Apache Airflow
> Issue Type: Bug
> Components: scheduler
> Affects Versions: 1.9.0
> Reporter: Slawomir Krysiak
> Assignee: Alex Lumpov
> Priority: Major
> Attachments: Screen Shot 2018-04-20 at 5.04.12 PM.png
>
>
> Hi,
>
> It would be nice to be able to modify the period range (a.k.a start_date) per
> dag/subdag and have scheduler pick it up. Not sure if that should be a
> feature request or a bug, but I was under the assumption that it works that
> way already. But for some reason it doesn't seem to be the case in 1.9.0
> which I'm using for my POC. Attaching my message from gitter... BTW, it seems
> that there's so many questions coming up on that channel but they don't seem
> to be addressed promptly.
> Thanks,
> Slawomir
>
> P.S. It would probably be helpful to be able to submit an 'end_date'
> parameter to DAG/SubDAG... there may be datasets that are no longer produced,
> yet they still have some period range extracted. Evolving transformation
> pipelines would definitely benefit from this kind of option.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
