fat-catTW opened a new pull request, #63624:
URL: https://github.com/apache/airflow/pull/63624

    <!-- 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.
   
   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
   -->
   related: #53046
   ---
   ## Description
   Implemented the `consuming_asset` filter for DAG runs, allowing users to 
filter DAG runs by consumed asset name or URI.
   
   ## Main Changes
   
   ### Backend Implementation
   - Added `_ConsumingAssetFilter` class in 
`airflow-core/src/airflow/api_fastapi/common/parameters.py`
   - Supports searching by asset name (exact or fuzzy match)
   - Supports searching by asset URI (exact or fuzzy match)
   - Supports partial URI matching
   
   ### API Endpoint
   - Added `consuming_asset` query parameter to `/dags/~/dagRuns` endpoint in 
`airflow-core/src/airflow/api_fastapi/core_api/routes/public/dag_run.py`
   - Parameter accepts string values to filter DAG runs that consume specific 
assets
   
   ### Frontend Integration
   - Added filter UI component in 
`airflow-core/src/airflow/ui/src/pages/DagRunsFilters.tsx`
   - Configured filter options in 
`airflow-core/src/airflow/ui/src/constants/filterConfigs.tsx`
   - Auto-generated OpenAPI schema and TypeScript types
   - Updated type definitions in 
`airflow-core/src/airflow/ui/src/utils/useFiltersHandler.ts`
   
   ## Testing
   - All 62 tests passing in 
`airflow-core/tests/unit/api_fastapi/core_api/routes/public/test_dag_run.py`
   - Added 6 comprehensive test cases for `TestGetDagRuns::test_filters` 
covering:
     - Search by asset name (e.g., `sales_data`)
     - Search by asset URI (e.g., `s3://bucket/sales`)
     - Partial URI matching (e.g., `s3://bucket` returns multiple results)
     - No results case (e.g., `nonexistent_asset` returns empty list)
   
   
   ##### 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".
   -->
   
   - [X] Yes (please specify the tool below)
   
   
   Generated-by: Claude 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]

Reply via email to