Why does dvc pull calculate its own MD5 hash?

I don’t understand why the dvc pull command takes the time (which can be significant it seems) to calculate its own MD5 hash. Couldn’t it just trust the remote? Could there be an option to tell it to trust the remote?

1 Like

@bemccarty yes, I think is the way it’s designed. It checks data consistency. Please, could you create a feature request on Github to start the discussion how can we implement an option?

Done: https://github.com/iterative/dvc/issues/2676

1 Like