Skip to content

Manually triggered dags should have default logical_date and run_after of "right now" #48412

@dstandish

Description

@dstandish

Body

As part of the AIP-83 amendment process we decided to make logical_date nullable, and to make it default null for manually triggered dags.

We got some feedback that this will suck for users.

So we want to keep the airlfow 2 behavior where logical_date is now() by default, but the users can optionally select null.

NOTE: This will have a UI component!!!

We will need to update the UI date picker so that user can optionally choose null.

  1. Manually triggering DAG Run via UI
  • date picker will default to the time when modal opened
  • user can null it out somehow
  • bonus if there's a button to clear the date
  1. Triggering Dag Run via API
  • try to make it so if not supplied then it will be timezone.now() but if supplied we respect it. if this causes trouble and is more or less impossible to support (1), then we can keep it required
  1. Trigger Dag Run Operator usage* if unset, it should take the logical date (yes, even if nullable) from the triggering dag run
  • if set, respect it no matter what

Committer

  • I acknowledge that I am a maintainer/committer of the Apache Airflow project.

Metadata

Metadata

Assignees

Labels

area:UIRelated to UI/UX. For Frontend Developers.kind:featureFeature Requestskind:metaHigh-level information important to the communitypriority:highHigh priority bug that should be patched quickly but does not require immediate new release

Type

No type

Projects

No projects

Milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions