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

[Remote Store] Move existing S3 APIs to use S3AsyncService #11985

Open
gbbafna opened this issue Jan 23, 2024 · 0 comments
Open

[Remote Store] Move existing S3 APIs to use S3AsyncService #11985

gbbafna opened this issue Jan 23, 2024 · 0 comments
Labels
enhancement Enhancement or improvement to existing feature or request Storage:Durability Issues and PRs related to the durability framework Storage:Performance

Comments

@gbbafna
Copy link
Collaborator

gbbafna commented Jan 23, 2024

Is your feature request related to a problem? Please describe

As of today only multipart upload uses AsyncService , which uses Netty Event loop based async IO . We should move existing APIs like List , Get , Delete etc as well to AsyncService .

Describe the solution you'd like

Create new APIs for async list/delete or modify current ones to use AsyncService.

Related component

Storage:Remote

Describe alternatives you've considered

No response

Additional context

No response

@gbbafna gbbafna added enhancement Enhancement or improvement to existing feature or request untriaged and removed untriaged labels Jan 23, 2024
@gbbafna gbbafna added Storage:Durability Issues and PRs related to the durability framework and removed untriaged Storage:Remote labels Jan 23, 2024
@rramachand21 rramachand21 moved this from 🆕 New to Ready To Be Picked in Storage Project Board Mar 8, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement Enhancement or improvement to existing feature or request Storage:Durability Issues and PRs related to the durability framework Storage:Performance
Projects
Status: Ready To Be Picked
Development

No branches or pull requests

3 participants