I wanted to ask before I spend a few hours enhancing my custom IO Manager: has anyone already written their own version including support for asset versions? They’re passed to the

OutputContext

, meaning different versions could be written into different paths, and it should be fairly easy to pass a version metadata into

AssetIn

to specify which version of the asset should be read downstream.

I'm not aware of one FWIW. Although if you model each version as a partition, the default IO managers should handle this

Thanks Sandy, I thought of partitions but was thinking of something more analogous to this discussion on dbt-core, where a downstream asset could specify which upstream version it fetches. I guess this could work with some partition mapping, but I’d still need to think a little more about the implementation details.