xichen01 commented on PR #6589: URL: https://github.com/apache/ozone/pull/6589#issuecomment-2650669457
@mohan3d > @Tejaskriya I didn't think of such case. Maybe @ivandika3 and @xichen01 can help more on this. AWS S3 buckets do not have the concept of directories, so for FSO buckets we can define the behavior of Lifecycle deletion. A simple way is to define all deletions as recursive deletions, so that there will be no problem of being unable to delete because the directory is not empty. > Initially I remember I implemented it this way, if the user who sat the lifecycle configuration doesn't have the right to delete the key, then the key should be skipped although it was eligible for deletion. > > But later I changed it to delete the key anyway, I need to check the code to answer you accurately. The thread that performs the delete operation can have ozone admin privileges, so it can delete any key -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
