[GitHub] [airflow] dstandish commented on pull request #25013: Show 'dataset-triggered' as schedule interval for dataset-triggered dags

[GitBox <gi...@apache.org>]

dstandish commented on PR #25013:
URL: https://github.com/apache/airflow/pull/25013#issuecomment-1183553844

   Re changing the column name from "schedule" to trigger", i think it's  a reasonable thing to explore and consider but don't want to take that  on here.  I just want to add a quick messaging fix.  And in the meantime, I don't think that conceptially we're in such a terrible, contradictory place.  Even a timetable, could have a very irregular scheduling cadence, could even be entirely random.  We can think of "scheduling" as the rules by which it's determined when a dag is set to run.  So the run for a dataset-triggered dag is "scheduled" when its upstream datasets are updated -- it's "scheduling" is determined by dataset events.  @blag could you possibly  create a card in the project to represent this concern as a work item? And we can pick it up as availability and priority dictate?


-- 
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: commits-unsubscribe@airflow.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org