You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
#280 adds a high level diff tool for one table at a time. What we would like to have for staging (or feature branches) is a tool that can efficiently diff everything against master. To do so we don't want to calculate diffs for every file in the catalog twice, so I think we should first check md5 hashes (do we have those on the file level already?) and then compare them against a target catalog. It would be great if that catalog could be our main remote one as well (I think S3 can provide md5 hashes for files without having to download them?).
It would also be good to have the ability to check only a subset of all tables with this tool (e.g. everything in garden/OWID)
The text was updated successfully, but these errors were encountered:
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
#280 adds a high level diff tool for one table at a time. What we would like to have for staging (or feature branches) is a tool that can efficiently diff everything against master. To do so we don't want to calculate diffs for every file in the catalog twice, so I think we should first check md5 hashes (do we have those on the file level already?) and then compare them against a target catalog. It would be great if that catalog could be our main remote one as well (I think S3 can provide md5 hashes for files without having to download them?).
It would also be good to have the ability to check only a subset of all tables with this tool (e.g. everything in garden/OWID)
The text was updated successfully, but these errors were encountered: