Adds stale status filtering capability to the asset catalog UI #27886
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Adds stale status filtering capability to the asset catalog UI, allowing users to filter assets based on their stale status (Fresh, Stale, Missing). This improves asset monitoring and management by making it easier to identify assets that need attention. ## Changes - Add stale status to asset GraphQL fragment - Implement new `useStaleStatusFilter` hook with status indicators - Update `useAssetDefinitionFilterState` to handle stale status filters - Add stale status filter to asset catalog filtering UI - Add test coverage for stale status filtering - Update data version logic to handle partitioned assets without specified partitions - Add test for stale status behavior with partitioned assets ## Test Plan - Added unit tests for stale status filtering functionality - Added test cases for partitioned asset stale status behavior - Existing test coverage maintained and expanded ## Related Builds on existing asset filtering infrastructure and stale status tracking capabilities. Related to issue dagster-io#27276 but doesn't really cover it, the issue request is about asset status case (Failed, Materialized, Etc.) but It was very difficult to add it, maybe the logic for status cases should be passed to the python resolver server instead of graphQL to reuse it on filters. ## How I Tested These Changes - Added test + UI exploring on example repo ## Changelog > Added stale status filter on asset catalog
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary & Motivation
Adds stale status filtering capability to the asset catalog UI, allowing users to filter assets based on their stale status (Fresh, Stale, Missing). This improves asset monitoring and management by making it easier to identify assets that need attention.
Changes
useStaleStatusFilterhook with status indicatorsuseAssetDefinitionFilterStateto handle stale status filtersTest Plan
Related
Builds on existing asset filtering infrastructure and stale status tracking capabilities.
Related to issue #27276 but doesn't really cover it, the issue request is about asset status case (Failed, Materialized, Etc.) but It was very difficult to add it, maybe the logic for status cases should be passed to the python resolver server instead of graphQL to reuse it on filters.
How I Tested These Changes
Changelog