errose28 commented on PR #3966: URL: https://github.com/apache/ozone/pull/3966#issuecomment-1317839443
Another issue is that `ozone.client.fs.default.bucket.layout` defaults to FSO. Even in master right now this means if a bucket is created using ofs while the OM is pre-finalized, it will fail unless this config is set to LEGACY. If we want to avoid this we could make the fs layout config default to an empty value, which will use the server side default layout if the client side one is unset. This allows the OM to use LEGACY for everything when pre-finalized and switch to using the server default once finalized. This would make the upgrade process smoother, but would mean that if someone set the default server side layout to OBS, they would need to explicitly set this config to FSO otherwise creating a bucket as part of mkdir would fail. IMO this would be better than a surprise during upgrade, and is also similar to what I am currently planning to do on s3 gateway in #3967. However, with 1.3.0 almost out the door and given the scope of test failures in this PR I don't think this will land in the release. -- 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]
