Inherit the run_ordering from DatasetTriggeredTimetable for DatasetOrTimeSchedule

[sunank200]

• Inherit the run_ordering from DatasetTriggeredTimetable for DatasetOrTimeSchedule

---

^ Add meaningful description above
Read the Pull Request Guidelines for more information.
In case of fundamental code changes, an Airflow Improvement Proposal (AIP) is needed.
In case of a new dependency, check compliance with the ASF 3rd Party License Policy.
In case of backwards incompatible changes please leave a note in a newsfragment file, named {pr_number}.significant.rst or {issue_number}.significant.rst, in newsfragments.

[bbovenzi]

Why do we want to change it on CronTrigger instead of on DatasetOrTimeSchedule?

[sunank200]

Why do we want to change it on CronTrigger instead of on DatasetOrTimeSchedule?

DatasetOrTimeSchedule for example uses the reordering timetable object as per https://github.com/apache/airflow/blob/main/airflow/timetables/datasets.py#L55 For example:

schedule=DatasetOrTimeSchedule(
        timetable=CronTriggerTimetable("* * * * *", timezone="UTC"), datasets=(dag1_dataset & dag2_dataset)
    ),

[bbovenzi]

@uranusjr Does this make sense to you?

[sunank200]

@uranusjr Does this make sense to you?

@bbovenzi I have added the reordering for DatasetOrTimeSchedule now.

[vatsrahul1001]

@sunank200 tested, LGTM

[dstandish]

nice job finding the problem @sunank200