Skip to content
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.

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

Add option to not copy images and avoid content-based-uuid by default. #93

Open
Erotemic opened this issue Apr 19, 2024 · 0 comments
Open

Comments

@Erotemic
Copy link
Owner

The way that images are ingested into the system is poorly designed. I believe that it forces a copy of the image into its internal database and generates a UUID based on the hash of the image. This is a lot of overhead and it is not necessary for many applications.

There should be an option to enable or disable this behavior. If the behavior is disabled it should use a random uuid.

I think some of the above might be in a partially-implemented state, but in any case we need to make it clear if image ingest is in "copy-mode" or "in-situ" mode (or maybe "lazy" mode?). Similarly, the uuid can just be a random one. If we want to do content based hashing, that is a good idea, but it has to be an option that defaults to off.

I don't think I have the bandwidth to implement this in the near future. Looking for someone who wants to help with it.

@Erotemic Erotemic changed the title Add option to not copy images / create uuids Add option to not copy images and avoid content-based-uuid by default. Apr 19, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant