Description
What's the use case?
Encountered a situation when updating a codebase from using CalVer to SemVer where all code versions across the repo were bumped. We use a helper utility which propagates code versions up through functions so if any function that an asset depends on gets changed then the asset code version also does. The SemVer/CodeVer switch triggered this across the board. Ideally it would be possible via the UI to dismiss asset staleness etc, rather than needing to create fake materialization events.
Ideas of implementation
No response
Additional information
Also encountered this in the past when we changed the DB schema on a very expensive ingestion operation. Manually modifying the DB table to be compatible with the new schema was much more time efficient, but then all older partitions yelled at me!
Message from the maintainers
Impacted by this issue? Give it a 👍! We factor engagement into prioritization.