Open nathanjmcdougall opened 3 months ago
I've just been thinking about whether there was anything to be done about code versioning, and this looks like a great idea, thanks!
Should be straightforward to implement without breaking existing caches.
I think an analogous argument to the task decorator would be good, and it would keep consistency between the tools.
I considered whether hashing the task's code would work, but you'd run into issues with changes that don't affect output and with dependency code.
On Mon, 29 July 2024, 11:35 Nathan McDougall, @.***> wrote:
Often the run function is being modified in between runs, which invalidates the cache.
Dagster copes with this by having the user maintain a hard coded version in the decorator: https://docs.dagster.io/guides/dagster/asset-versioning-and-caching
I think labtech could do something similar, to enable automatic cache invalidation.
— Reply to this email directly, view it on GitHub https://github.com/ben-denham/labtech/issues/26, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAN25UYJZNGVUPOU2YJXFE3ZOV54PAVCNFSM6AAAAABLTGRMA6VHI2DSMVQWIX3LMV43ASLTON2WKOZSGQZTIMJWGMYDEMI . You are receiving this because you are subscribed to this thread.Message ID: @.***>
Often the
run
function is being modified in between runs, which invalidates the cache.Dagster copes with this by having the user maintain a hard coded version in the decorator: https://docs.dagster.io/guides/dagster/asset-versioning-and-caching
I think labtech could do something similar, to enable automatic cache invalidation.