ozone
ozone copied to clipboard
apache
HDDS-8342. AWS S3 Lifecycle Configurations doc
What changes were proposed in this pull request?
Design proposal for data retention (AWS S3 Lifecycle Configurations ) feature. Please comment inline on the markdown document to ask questions and post feedback.
What is the link to the Apache JIRA
How was this patch tested?
N/A
@ivandika3 @xichen01 Please take a look and let me know whether I need to amend or enhance it.
@ArafatKhan2198 @SaketaChalamchala @tanvipenumudy Could you help take a look as well when you have time?
@mohan3d , thanks for working on this. The design documents looks straightforward. Could you fill it with more details? such as the new table format, how to handle the scale thing, the rule example, and what will be the final decision if multiple rules are defined. BTW, I prefer a new table too.
Thanks @ChenSammi for the review, I am not able to respond to your latest comment so I will do here.
@mohan3d , thanks for working on this. The design documents looks straightforward. Could you fill it with more details? such as the new table format, how to handle the scale thing, the rule example, and what will be the final decision if multiple rules are defined. BTW, I prefer a new table too.
Sure, I will be adding the new table format shortly, and more details on how the retention manager is designed (This should help us understand how it can scale and also a good opportunity to get some thoughts from the community).
how to handle the scale thing, the rule example, and what will be the final decision if multiple rules are defined.
This was answered in earlier comment.
@ChenSammi @SaketaChalamchala @xichen01 I forgot to submit my comments earlier and it was in the pending status. Please take a look into my comments.
@mohan3d
At the time of implementing this I had no imagination on how the ACLs will work on this. If I recall it was restricted for the owner.
Yes, If we restrict that only the bucket owner can set a lifecycle, we can circumvent the permission issue when lifecycle-service delete keys, because the bucket owner have ALL Permission for the bucket resources.
