imrichardwu opened a new pull request, #68369:
URL: https://github.com/apache/airflow/pull/68369
- Introduced new API endpoint `/ui/calendar/{dag_id}/deadlines` to retrieve
aggregated deadline counts for a DAG, categorized by deadline time and missed
status.
- Added data models `CalendarDeadlineResponse` and
`CalendarDeadlineCollectionResponse` to structure the response data.
- Implemented the `get_deadline_calendar_data` method in `CalendarService`
to handle the logic for fetching deadline data.
<!-- SPDX-License-Identifier: Apache-2.0
https://www.apache.org/licenses/LICENSE-2.0 -->
<!--
Thank you for contributing!
Please provide above a brief description of the changes made in this pull
request.
Write a good git commit message following this guide:
http://chris.beams.io/posts/git-commit/
Please make sure that your code changes are covered with tests.
And in case of new features or big changes remember to adjust the
documentation.
For user-facing UI changes, please attach before/after screenshots (or a
short
screen recording) so reviewers can assess the visual impact.
Feel free to ping (in general) for the review if you do not see reaction for
a few days
(72 Hours is the minimum reaction time you can expect from volunteers) - we
sometimes miss notifications.
In case of an existing issue, reference it using one of the following:
* closes: #ISSUE
* related: #ISSUE
-->
This adds `/ui/calendar/{dag_id}/deadlines`, which returns deadline counts
grouped by calendar bucket and missed status. The endpoint supports the same
`hourly` / `daily` granularity and `deadline_time` range filters used by the
Calendar UI, so the frontend can overlay deadline status on top of the existing
Dag run calendar.
The goal for the UI is to make deadlines visible in context: Calendar cells
can show whether a time bucket has upcoming or missed deadlines, tooltips can
include deadline counts, and the legend can explain the deadline markers
without replacing the existing Dag run density view.
Changes include:
- new deadline calendar response models
- a calendar service query that aggregates `Deadline` rows by
`deadline_time` bucket and `missed`
- a new private UI route for calendar deadline data
- OpenAPI schema updates and regenerated UI client types/hooks
Implemented deadline in calendar based on the details in
PR(https://github.com/apache/airflow/issues/50501#issuecomment-3962289911)
---
##### Was generative AI tooling used to co-author this PR?
<!--
If generative AI tooling has been used in the process of authoring this PR,
please
change below checkbox to `[X]` followed by the name of the tool, uncomment
the "Generated-by".
-->
- [ ] Yes (please specify the tool below)
<!--
Generated-by: [Tool Name] following [the
guidelines](https://github.com/apache/airflow/blob/main/contributing-docs/05_pull_requests.rst#gen-ai-assisted-contributions)
-->
---
* Read the **[Pull Request
Guidelines](https://github.com/apache/airflow/blob/main/contributing-docs/05_pull_requests.rst#pull-request-guidelines)**
for more information. Note: commit author/co-author name and email in commits
become permanently public when merged.
* For fundamental code changes, an Airflow Improvement Proposal
([AIP](https://cwiki.apache.org/confluence/display/AIRFLOW/Airflow+Improvement+Proposals))
is needed.
* When adding dependency, check compliance with the [ASF 3rd Party License
Policy](https://www.apache.org/legal/resolved.html#category-x).
* For significant user-facing changes create newsfragment:
`{pr_number}.significant.rst`, in
[airflow-core/newsfragments](https://github.com/apache/airflow/tree/main/airflow-core/newsfragments).
You can add this file in a follow-up commit after the PR is created so you
know the PR number.
--
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]
