errose28 commented on PR #6385: URL: https://github.com/apache/ozone/pull/6385#issuecomment-2036011365
@sodonnel I think it would help if you were to write up a markdown document summarizing the new API and contribute that as its own PR that people could read and comment as an easier medium for discussion. A lot of the discussion happening on this PR is not related to the code, but to higher level design decisions that were made like ACL handling, tracking ID throughout the process, and the API name and spec itself. There may be good reason for doing it this way, but for myself and others in the community both now and in the future, it would be best to write out the options that were considered and why a given approach was chosen, rather than submitting code that has already made a lot of these decisions without showing the process to get there. Some things that might be helpful to write out: - What does the new API look like from the client side - How will clients use the new API - How does the API compare to what other storage systems offer? Are there any ideas there we can re-use? - General correctness guarantees in terms of metadata and data - What key metadata is preserved or updated at the time of create and commit More generally I hope this extra step can become a normal part of any change having moderate impact, like a new client API we must support indefinitely. -- 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]
