umamaheswararao commented on pull request #2927: URL: https://github.com/apache/ozone/pull/2927#issuecomment-998392478
This is a very good point @sodonnel. Similar lines, one idea is to have versioning of bucket default config. Client can have grandfather version. When someone sends with grandfather version, we always take it. Otherwise highest version number should take preference. Let's say bucket has replication config with version1 and someone modified it so we can increment the version to 2. Now when older client who was holding the bucket with version1 replication config, will still pass that replication config, but server knows it's modified and can use that version2. But the problem is about the transparency. Client still does not know its using different config at the server silently. This needs more discussion I feel. -- 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]
