New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Cached catalog #162

Open

vijayvammi opened this issue Nov 23, 2024 · 0 comments

Collaborator

vijayvammi commented Nov 23, 2024 •

edited

Loading

To solve the problem of sourcing data and also managing large datasets. Bring in a cached catalog.

The behaviour is as follows:

In either GET or PUT, we do not actually move any files around.

For any of the contents in the GET, we keep track of the MD5 hash of the files.
Same for PUT, we keep track of the MD5 hash.

Open question, should we keep the hash of input files and output files of all or only the changed ones?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment