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

Cache object stores per postgres session #93

Open

aykut-bozkurt opened this issue Jan 10, 2025 · 0 comments · May be fixed by #99

Labels

Collaborator

aykut-bozkurt commented Jan 10, 2025

Now, we create a new object store per copy operation. That is costly, especially if you use token based auth (you request a new token per each copy).

We can cache object stores per postgres session. Probably per bucket (or container) as different buckets generally have different credentials.

aykut-bozkurt added the enhancement label

aykut-bozkurt linked a pull request

that will close this issue

Cache object stores per scheme + bucket #99

Open

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