Skip to content

Cache object stores per postgres session #93

@aykut-bozkurt

Description

@aykut-bozkurt

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.

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions