We still have tasks in production that use this feature. Sometimes, it has been used for one off tasks that create simple static mapping tables (Tables loaded from a static file that also lives in source control, creating a programmatically generated time dimension etc...).
Of course, maybe just having the task in question as a script that uses the airflow utilities would be sufficient. Best, Arthur On Tue, May 17, 2016 at 10:40 AM, Chris Riccomini <criccom...@apache.org> wrote: > @Bolke/@Jeremiah > > When you make your changes to unify the backfiller and scheduler, it sounds > like this can go away, right? > > On Tue, May 17, 2016 at 10:38 AM, Maxime Beauchemin < > maximebeauche...@gmail.com> wrote: > > > The scheduler won't trigger where `adhoc=True`. The CLI's > backfill/test/run > > is the only way to trigger where `adhoc=True`. For backfill specifically, > > there's a `-a`, `--include_adhoc` flag to make these tasks in-scope to > the > > backfill. > > > > Max > > > > On Tue, May 17, 2016 at 10:14 AM, Chris Riccomini <criccom...@apache.org > > > > wrote: > > > > > Hey all, > > > > > > Curious about what the 'adhoc' property is in BaseOperator. It appears > to > > > be completely undocumented. What is this? > > > > > > Cheers, > > > Chris > > > > > >
