blag commented on PR #25013: URL: https://github.com/apache/airflow/pull/25013#issuecomment-1183536355
Does it make sense to continue calling the column "Schedule" if some rows might be triggered by only dataset events? Or should we do something like this: | Trigger | Last Run | Next Run | | ------- | --------- | --------- | | `Schedule: @daily` | ... | ... | | (none) | | | | `Dataset: <dataset-uri>` | ... | | I can also see a use case for having a DAG be triggered by both dataset events and by schedule events, like refining an ML model every night and applying that model to live data the next day as it passes through. So a DAG trigger could be displayed as: `Schedule: @daily`, `Dataset: <dataset-uri>` If we're worried about the `Schedule: ` or `Dataset: ` prefixes causing unnecessary visual noise, we can simply elide them if all displayed DAG triggers are from the same source (eg: if all DAGs are triggered on schedules, just display `@daily`, with no `Schedule: ` prefix). -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
