Skip to content

[Filters] Add filters to Search - Assets #53052

Open

Description

@cmarteepants

View

Search – Assets

Image

Filters to Add

  • Filter by Asset Group
    ↪ Narrow results to a logical grouping of assets (e.g., revenue_reporting, customer_metrics)

  • Filter by Consuming DAG and / or Producing Task
    ↪ Quickly locate assets by their upstream producer or downstream consumer

  • Filter by Last Event Timestamp (Range)
    ↪ Identify stale or recently updated assets

  • Filter by Is Alias (Yes/No)
    ↪ Distinguish between assets vs. placeholders

  • Filter by Has Events (Yes/No)
    ↪ Distinguish between assets with active data lineage vs inactive definitions

API Support

⚠️ Partial

  • The assets API supports filtering by:
    • dag_id, task_id, and sometimes group
  • Currently lacks:
    • Filtering by event presence (has_events)
    • Range filtering by last event timestamp

UI Impact

  • Add a filter panel above the asset list table
  • Useful in large deployments with hundreds or thousands of assets

Notes

  • Enables users to answer critical questions like:
    • “What assets are stale?”
    • “Which DAGs produce assets in this domain?”
  • Especially helpful when debugging broken pipelines or validating asset freshness

Activity

  1. added
    kind:metaHigh-level information important to the community
    area:UIRelated to UI/UX. For Frontend Developers.
    and removed
    kind:metaHigh-level information important to the community
    on Jul 8, 2025
  2. jroachgolf84 commented on Jul 22, 2025

    @jroachgolf84
    Collaborator

    Something similar here: #47164.

  3. jroachgolf84 commented on Jul 22, 2025

    @jroachgolf84
    Collaborator

    Filter by Asset Group
    ↪ Narrow results to a logical grouping of assets (e.g., revenue_reporting, customer_metrics)

    @cmarteepants, is there currently a way to assign an Asset to a "group"?

  4. cmarteepants commented on Jul 23, 2025

    @cmarteepants
    CollaboratorAuthor

    @jroachgolf84 there is an arg for it, but it's not currently being reflected in the UI. Probably 3.2 when we revamp it.

  5. nikhil25803 commented on Jul 31, 2025

    @nikhil25803

    Hey @cmarteepants and @jroachgolf84, I'd like to work on this. Can you please assign it to me?
    Additionally, issue #53053 is somewhat related. Can I also pick that up, along with this issue?

  6. vatsrahul1001 commented on Aug 11, 2025

    @vatsrahul1001
    Contributor

    @nikhil25803, how are we progressing on this?

  7. nikhil25803 commented on Aug 11, 2025

    @nikhil25803

    Hey @vatsrahul1001, I faced some issues while setting up the repo 😅, but I managed to do it. I'm working on it and will try to raise a PR by Sunday this week.

  8. pierrejeambrun commented on Aug 11, 2025

    @pierrejeambrun
    Member

    @nikhil25803 Great to hear, looking forward to it 🎉

  9. pierrejeambrun commented on Aug 21, 2025

    @pierrejeambrun
    Member

    We need an order_by latest_asset_event_timestamp too. last_asset_event.timestamp

  10. potiuk commented on Mar 2, 2026

    @potiuk
    Member

    @nikhil25803 We are unassigning you from this issue as part of our updated assignment policy.

    This is not meant to discourage your contribution — quite the opposite! You are still very welcome to work on this issue and submit a PR for it. Simply comment that you are working on it and open a PR when ready.

    We found that formal assignments were not working well, as they often prevented others from contributing when the assignee was not actively working on the issue.

  11. jroachgolf84 commented on May 18, 2026

    @jroachgolf84
    Collaborator

    @cmarteepants - what do you mean by this:

    Filter by Asset Group
    ↪ Narrow results to a logical grouping of assets (e.g., revenue_reporting, customer_metrics)

    Is there a way to specify an "Asset Group"? In the UI right now, it just says "asset".

  12. Ayan-Amir commented on Aug 11, 2026

    @Ayan-Amir

    Hi, I'd like to work on this.

    The API doesn't yet support has_events or last-event-timestamp rangefiltering, so I'll scope my first PR to what's already there: Consuming DAG and Producing Task, following the pattern from the completed sibling issues under #53040.

    Leaving Asset Group out for now, as @jroachgolf84's question about it is still open.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions