What some people do is give the new dag a new version in the name, like _v1 or _v2 at the end. Then it's treated like another dag and you can disable the old one. IF you make changes to dags, it's possible that old operators/tasks are no longer visible in the UI and you no longer have access to the log files.
Obviously, it's important to use the correct start_date in that case and probably turn off the old version. Rgds, Gerard On Tue, Oct 25, 2016 at 12:09 PM, <[email protected]> wrote: > Hi David, > > For me worked: > 1. Disable the DAG > 2. Refresh > 3. Edit the schedule_interval > 4. Refresh the DAG > 5. Enable > > You also should edit the start_date to avoid backfilled runs. > > --alex > > -- > B: mapredit.blogspot.com > > From: David Batista > Sent: Tuesday, October 25, 2016 11:48 AM > To: [email protected] > Subject: Changing the crontab for a DAG > > Hi everyone, > > Just a quick question, if you have a running DAG (i.e., runs daily for > instance), and at a certain point you want to update the crontab, for > instance, change the hour on which it runs. > > Usually, want I do, is to clear all the past tasks with the old crontab, > and update the the start_date of the DAG, to be equal to the day when the > the hour changed. > > Nevertheless, sometimes, it happens that the DAG starts running with the > old hour (before the change) > > What is the best way to deal with this, changing, let's say the hour, for a > running a DAG? > > Best regards, > David Batista > > -- > > [image: logo] > <http://www.facebook.com/hellofreshde> <http://twitter.com/ > HelloFreshde> > <http://instagram.com/hellofreshde/> <http://blog.hellofresh.de/> > <https://app.adjust.com/ayje08?campaign=Hellofresh& > deep_link=hellofresh%3A%2F%2F&post_deep_link=https%3A%2F% > 2Fwww.hellofresh.com%2Fapp%2F%3Futm_medium%3Demail%26utm_ > source%3Demail_signature&fallback=https%3A%2F%2Fwww. > hellofresh.com%2Fapp%2F%3Futm_medium%3Demail%26utm_source% > 3Demail_signature> > > *HelloFresh App –Download Now!* > <https://app.adjust.com/ayje08?campaign=Hellofresh& > deep_link=hellofresh%3A%2F%2F&post_deep_link=https%3A%2F% > 2Fwww.hellofresh.com%2Fapp%2F%3Futm_medium%3Demail%26utm_ > source%3Demail_signature&fallback=https%3A%2F%2Fwww. > hellofresh.com%2Fapp%2F%3Futm_medium%3Demail%26utm_source% > 3Demail_signature> > *We're active in:* > US <https://www.hellofresh.com/?utm_medium=email&utm_source= > email_signature> > | DE > <https://www.hellofresh.de/?utm_medium=email&utm_source=email_signature> | > UK > <https://www.hellofresh.co.uk/?utm_medium=email&utm_source=email_signature > > > | NL > <https://www.hellofresh.nl/?utm_medium=email&utm_source=email_signature> | > AU > <https://www.hellofresh.com.au/?utm_medium=email&utm_ > source=email_signature> > | BE > <https://www.hellofresh.be/?utm_medium=email&utm_source=email_signature> | > AT <https://www.hellofresh.at/?utm_medium=email&utm_source=email_signature > > > | CH > <https://www.hellofresh.ch/?utm_medium=email&utm_source=email_signature> | > CA <https://www.hellofresh.ca/?utm_medium=email&utm_source=email_signature > > > > www.HelloFreshGroup.com > <http://www.hellofreshgroup.com/?utm_medium=email&utm_ > source=email_signature> > > We are hiring around the world – Click here to join us > <https://www.hellofresh.com/jobs/?utm_medium=email&utm_ > source=email_signature> > > -- > > <https://www.hellofresh.com/jobs/?utm_medium=email&utm_ > source=email_signature> > HelloFresh AG, Berlin (Sitz der Gesellschaft) | Vorstände: Dominik S. > Richter (Vorsitzender), Thomas W. Griesel, Christian Gärtner | Vorsitzender > des Aufsichtsrats: Jeffrey Lieberman | Eingetragen beim Amtsgericht > Charlottenburg, HRB 171666 B | USt-Id Nr.: DE 302210417 > > *CONFIDENTIALITY NOTICE:* This message (including any attachments) is > confidential and may be privileged. It may be read, copied and used only by > the intended recipient. If you have received it in error please contact the > sender (by return e-mail) immediately and delete this message. Any > unauthorized use or dissemination of this message in whole or in parts is > strictly prohibited. > >
