Hi everyone, just a quick basic question, as I am new to dagster: I need a simple data versioning in the sense that every time an asset is materialized a copy is stored to a "history store" for possible later inspection. Is there a best practice in dagster to achieve that? (Of course I can implement it in the op, but there might be a more elegant way)
12/13/2022, 12:53 AM
Hi @andi.d - we don't currently have built-in support for that. You would need to implement your own I/O manager that does that or do it within the body of the asset function
12/13/2022, 12:01 PM
Thanks for the reply! No worries, I will use the asset body for that.