Add run_id_pattern search for Dag Run API.

[noeunkim]

Feature

• Adds single run_id pattern filter to /dag_runs page
• Based on Feature Gap - UI/API Filters #52363
• This filter was available in previous version but is currently missing in v3

Discussion points

• Single run_id filter sufficient? or should we support more complex search parser?
  • e.g., AND / OR conditions
• Any suggestions for improving the UI design? more structured form preferable?

Feedback and suggestions are welcome!

---

^ 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 airflow-core/newsfragments.

[boring-cyborg]

Congratulations on your first Pull Request and welcome to the Apache Airflow community! If you have any issues or are unsure about any anything please check our Contributors' Guide (https://github.com/apache/airflow/blob/main/contributing-docs/README.rst)
Here are some useful points:

• Pay attention to the quality of your code (ruff, mypy and type annotations). Our pre-commits will help you with that.
• In case of a new feature add useful documentation (in docstrings or in docs/ directory). Adding a new operator? Check this short guide Consider adding an example DAG that shows how users should use it.
• Consider using Breeze environment for testing locally, it's a heavy docker but it ships with a working Airflow and a lot of integrations.
• Be patient and persistent. It might take some time to get a review or get the final approval from Committers.
• Please follow ASF Code of Conduct for all communication including (but not limited to) comments on Pull Requests, Mailing list and Slack.
• Be sure to read the Airflow Coding style.
• Always keep your Pull Requests rebased, otherwise your build might fail due to changes not related to your commits.
  Apache Airflow is a community-driven project and together we are making it better 🚀.
  In case of doubts contact the developers at:
  Mailing List: [email protected]
  Slack: https://s.apache.org/airflow-slack

[jscheffl]

If something in UI changes it is cool to always also add a screenshot - that makes review easier. Can you add some mugshot to PR description?

[jscheffl]

I am not fully sure about this feature, it is really a gap from previous version but the implementation only offers an exact match. No globbing.

I'd request some other reviewers as well, I assume next level is also we need to invest into better search capabilities in general, only exact run ID match is not much of a great value.

Please do not treat it tooo negative. I think in general the search capabilties are a shortcoming in the UI in general. I am unsure about the increments needed to get back to 2.11 state of options.

[jason810496]

Nice! Thanks for the PR, just a small nit. LGTM on API side after fix.

[fritz-astronomer]

That was fast! Awesome work.

There are a number of other fields that could be sorted on, and I agree with

only exact run ID match is not much of a great value

However, I do also think something is better than nothing?
Maybe can revisit at a later time to add something more generic and powerful for many fields across many models?

[pierrejeambrun]

Thanks for the pull request, that's a good idea.

We do support searching on patterns:

    DESCRIPTION = (
        "SQL LIKE expression — use `%` / `_` wildcards (e.g. `%customer_%`). "
        "Regular expressions are **not** supported."
    )

You can take a look at search_param_factory to construct such filters on the API side.

For instance for the task_display_name_pattern search.

[pierrejeambrun]

Nice, just a few nitpicks and should be good to merge.

Thanks for the pull request.

[pierrejeambrun]

One remark

[pierrejeambrun]

Two small nits and we should be good to merge.

[pierrejeambrun]

Also I think you took example on the TaskInstance page, where the Search Bar is first in the filters. This PR adds the SearchBar as last in the DagRun filter page. I think we should be consistent and put the search first in this page too.

[pierrejeambrun]

Nice, thanks

[noeunkim]

Nice, thanks

sorry for bothering you for the final step
It seems there is an issue on CI: https://github.com/apache/airflow/actions/runs/16147315558/job/45570359614
should I rebase to resolve this, or just keep retriggering?

Run # Catch errors in the download with || to avoid the whole workflow failing
error downloading cache-pre-commit-v4-3.10.18-728e39db9f8498b32d8121c0e563f645c7a2c9ed2da2fa53e2a59696c9f984df-main: 
HTTP 502: Server Error (https://api.github.com/repos/apache/airflow/actions/artifacts/3486535546/zip)```

[jscheffl]

Thanks! Also for staying on it with that amount of feedback! Hope we did not scare you in reviews.
LGTM!

[boring-cyborg]

Awesome work, congrats on your first merged pull request! You are invited to check our Issue Tracker for additional contributions.

[bbovenzi]

Great work!

[kyungjunleeme]

nice work!!