ChenSammi commented on PR #9255: URL: https://github.com/apache/ozone/pull/9255#issuecomment-3500146986
> @ChenSammi Thanks for the improvement. Left come comments. > > Since the OMBucketDeleteRequest will also delete the lifecycle configuration, technically the bucket object ID mismatch should not happen. However, it's good to double check. @ivandika3 , this is mainly for upgrade-downgrade-upgrade consideration. After discuss with Xi, we plan to not introduce new OM layout feature. In case of upgrade-downgrade-upgrade, to prevent a bucket with LifecycleConfiguration created during upgrade, but not finalized, then system is downgraded, this LifecycleConfiguration will be left in the DB table, then later the cluster is upgraded again. If the bucket is deleted before that, and a new bucket with same name is created, then this new bucket should not be linked to the LifecycleConfiguration in the DB table. -- 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]
