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

feat(s3): allow users to specify storage_class #1854

Merged
merged 4 commits into from
Apr 5, 2023

Conversation

knight42
Copy link
Contributor

@knight42 knight42 commented Apr 5, 2023

Fix #1751

This PR adds storage_class option to OpWrite and enables users to specify default storage_class or override it when using s3 backend.

Signed-off-by: Jian Zeng <anonymousknight96@gmail.com>
core/src/services/s3/backend.rs Outdated Show resolved Hide resolved
core/src/services/s3/backend.rs Outdated Show resolved Hide resolved
@Xuanwo
Copy link
Member

Xuanwo commented Apr 5, 2023

adds storage_class option to OpWrite

storage_class should not be added into OpWrite. Because users can't write code without knowing what's service it is. This violates OpenDAL's VISION.

Refer to RFC-1735 for our current design.

Signed-off-by: Jian Zeng <anonymousknight96@gmail.com>
Signed-off-by: Jian Zeng <anonymousknight96@gmail.com>
core/src/services/s3/backend.rs Outdated Show resolved Hide resolved
core/src/services/s3/backend.rs Outdated Show resolved Hide resolved
core/src/services/s3/backend.rs Outdated Show resolved Hide resolved
Signed-off-by: Jian Zeng <anonymousknight96@gmail.com>
Copy link
Member

@Xuanwo Xuanwo left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Great, thanks a lot!

@Xuanwo Xuanwo merged commit eca0e95 into apache:main Apr 5, 2023
@knight42 knight42 deleted the feat/s3-storage-class branch April 5, 2023 11:33
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

Successfully merging this pull request may close these issues.

Add default_storage_class for services s3
2 participants