sodonnel commented on pull request #2927: URL: https://github.com/apache/ozone/pull/2927#issuecomment-998604220
If we go with bucket config versioning, then the server should probably throw an exception if it receives a request with older config, prompting the client to refresh its config. Similar to "optimistic locking" when using databases. I suspect this may be a tricky change in the client at this stage. However, what value is there in passing the bucket config from the client to the server? If we always have to check the server anyway, we can avoid sending the bucket config from the client. We know there is a heirarchy of places the config can come from: 1. Key level setting supplied by the client. 2. Bucket Default 3. Cluster defaults - however this can be a client side default or server side default. I cannot remember what we decided on the client vs server default part. If the client sends two replicationConfig fields, both optional: 1. Key ReplicationConfig 2. Client Default Replication Config Then we don't need it to send the bucket level setting, as that is on the server anyway. On the server, we can apply the precedence rules and pick the correct setting accordingly. -- 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]
