Add exact-match uri filter to GET /assets endpoint

[seanmuth]

What

Adds a uri query parameter to GET /api/v2/assets that matches an asset by its exact URI, backed by a new single-column index on asset.uri.

Why

Today, resolving a single asset when you already know its full URI (for example, discovering an asset_id before posting to /assets/{asset_id}/events for cross-deployment dependencies) requires uri_pattern. That parameter compiles to ILIKE '%...%', which cannot use a B-tree index and degrades to a full table scan on large asset tables — the API docs themselves warn about this.

The Airflow 2 REST API offered a fast exact lookup via GET /datasets/{uri} (later GET /assets/{uri}), but it was not carried forward when the endpoint migrated to FastAPI under AIP-84 — the single-resource route became GET /assets/{asset_id} (integer PK only). This PR restores the exact-URI lookup as a query parameter.

Passing the URI as a query parameter rather than a path segment also avoids the URI-encoding problems path parameters have with the /, :, and %2F characters that asset URIs contain.

What changed

• New uri exact-match filter on GET /assets (equality comparison via the existing filter_param_factory).
• New non-unique index idx_asset_uri on asset.uri (the existing unique index leads with name and cannot serve uri-only lookups), with an Alembic migration.
• Regenerated OpenAPI spec + UI client, updated REVISION_HEADS_MAP and migration ref doc.
• Tests: exact-match hits plus negative cases confirming a substring does not match (unlike uri_pattern).

---

Was generative AI tooling used to co-author this PR?

• Yes — Claude Code (Opus 4.8, 1M context)

Generated-by: Claude Code (Opus 4.8, 1M context) following the guidelines

---

Drafted-by: Claude Code (Opus 4.8, 1M context) (no human review before posting)

---

Important

🛠️ Maintainer triage note for @seanmuth · by @potiuk · 2026-07-08 15:38 UTC

Helpful heads-up from the maintainers — please address before this PR can be reviewed:

• Pre-commit / static checks failing (CI image checks / Static checks). See the contributor guide.

Full criteria: Pull Request quality criteria.

The ball is in your court — you've been assigned to this PR. Fix the above, then mark it Ready for review.

_{Automated triage — may be imperfect; a maintainer takes the next look.}

[pierrejeambrun]

Thanks for the PR, makes sense!

A few suggestions bellow :)

[seanmuth]

Thanks for the review! Pushed 3c0560208b addressing all the points:

• Target version — retargeted the migration to 3.4.0: renamed to 0124_3_4_0_…, airflow_version="3.4.0", restored the 3.3.0 head and added a 3.4.0 entry in REVISION_HEADS_MAP, and updated the migration ref doc.
• Newsfragment — removed; agreed this isn't a behaviour change that needs a user warning.
• Description — trimmed to just the exact-match / indexed-equality note, dropped the comparison to the search params (they have their own docs).
• Multiple values — uri now accepts repeated params (?uri=a&uri=b) via FilterParam[list[str]] + ANY_EQUAL + default_factory=list, following the QueryTIStateFilter pattern. Added a test covering it. Agreed a list endpoint accepting multiple values is the right shape here.
• ORM comment — removed the API-layer reference from the model; kept the index (thanks for confirming 2.x had one).

Regenerated the OpenAPI spec + UI client. Locally the asset filter tests (14) and a fresh-DB up → down → up migration check both pass.

---

Drafted-by: Claude Code (Opus 4.8, 1M context) (no human review before posting)

[seanmuth]

Heads-up on CI: the only red check is CI image checks / Static checks, and it's unrelated to this PR. The failing hook is update-providers-build-files, which regenerates provider packaging files (apache/kafka, apache/flink, github, zendesk, microsoft/mssql, …) — this branch touches zero provider files (it's scoped to airflow-core assets API + a migration). It's pre-existing drift on main that any airflow-core PR triggering the --all-files static run inherits.

Everything substantive is green: the asset filter tests, mypy, ruff, migration/revision-heads checks, and the full test matrix all pass (138 passing). I also validated the change end-to-end on a local 3.2.1 env and a real Astro deployment (Runtime 3.2-4): exact ?uri= returns the single matching asset, repeated ?uri=a&uri=b returns both, a partial value correctly returns nothing, and uri_pattern still does its substring match.

This is ready for another look. Thanks again for the review!

---

Drafted-by: Claude Code (Opus 4.8, 1M context) (no human review before posting)

[pierrejeambrun]

Nice, thanks

LGTM, needs a rebase to fix conflicts, unrelated CI failures should go away too.