Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Remove execution_date from API, CLI, web UI return values #42339

Open
1 task done
uranusjr opened this issue Sep 19, 2024 · 0 comments
Open
1 task done

Remove execution_date from API, CLI, web UI return values #42339

uranusjr opened this issue Sep 19, 2024 · 0 comments
Assignees
@sunank200
Labels
AIP-83 Remove Execution Date Unique Constraint from DAG Run airflow3.0:candidate Potential candidates for Airflow 3.0 area:API Airflow's REST/HTTP API area:CLI area:UI Related to UI/UX. For Frontend Developers.
Milestone
Airflow 3.0.0

Comments

@uranusjr
Copy link
Member

Body

It should return the same value under logical_date. This field/attribute should already be present; if not, it should be added to the 2.x branch and released in 2.11.

Committer

  • I acknowledge that I am a maintainer/committer of the Apache Airflow project.
@uranusjr uranusjr added airflow3.0:candidate Potential candidates for Airflow 3.0 AIP-83 Remove Execution Date Unique Constraint from DAG Run labels Sep 19, 2024
@uranusjr uranusjr added this to the Airflow 3.0.0 milestone Sep 19, 2024
@dosubot dosubot bot added area:API Airflow's REST/HTTP API area:CLI area:UI Related to UI/UX. For Frontend Developers. labels Sep 19, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@sunank200 sunank200

Labels
AIP-83 Remove Execution Date Unique Constraint from DAG Run airflow3.0:candidate Potential candidates for Airflow 3.0 area:API Airflow's REST/HTTP API area:CLI area:UI Related to UI/UX. For Frontend Developers.
Projects
AIP-83 Remove execution date
Status: No status
Milestone
Airflow 3.0.0
Development

No branches or pull requests
2 participants
@uranusjr @sunank200