;> for each schedule *task *to have its own timetable override that's
>> processed within the dag run.
>>
>
> On Sun, Nov 7, 2021 at 6:34 PM Daniel Standish
> wrote:
>
>> A bit confused about what you're proposing Malthe.
>>
>> The thread subject is &q
On Sun, Nov 7, 2021 at 6:34 PM Daniel Standish wrote:
> A bit confused about what you're proposing Malthe.
>
> The thread subject is "task-level schedulling" but it says "there is no
> such interface to control
> task-level scheduling – or more specifically, the a
A bit confused about what you're proposing Malthe.
The thread subject is "task-level schedulling" but it says "there is no
such interface to control
task-level scheduling – or more specifically, the ability to control which
DAG runs to skip."
This makes it sound like y
tion date" that we can compare against.
>
>
>
> data_interval_start and/or data_interval_end are the dates you should use for
> such a purpose
>
> Please don't use the term execution date -- it is too overloaded and
> confusing.
>
> -ash
>
>
> On Mon
don't use the term execution date -- it is too overloaded and
confusing.
-ash
On Mon, Oct 18 2021 at 21:17:22 +, Malthe wrote:
While AIP-39 provides an interface for more powerful pluggable
scheduling behaviours, there is no such interface to control
task-level scheduling – or more s
While AIP-39 provides an interface for more powerful pluggable
scheduling behaviours, there is no such interface to control
task-level scheduling – or more specifically, the ability to control
which DAG runs to skip.
Examples:
- Skip task execution on certain days
- Skip task execution on
