rdblue edited a comment on pull request #3770: URL: https://github.com/apache/iceberg/pull/3770#issuecomment-1004455929
@jackye1995, it looks like we're mostly in agreement now: > 1. if it's better to have specific operation routes for non-RESTful operations > 2. head table/namespace operation with response, if we do that what set of fields should be in the response > 3. if pagination of response is needed when there are too many metadata log or snapshots > 4. progress tracking for table purge > 5. drop namespace cascade For 1, I think we're just trying to decide on the path for the `/tables/rename` route, right? I like the simplicity of `tables` and I don't think it will be confusing to have operation routes there. That's where I'd add multi-table transactions as well, which don't cleanly fit into a single REST resource. For 2, I think we should remove the HEAD request for namespaces and leave the tables HEAD request without response bodies. We're probably agreed? 3, 4, and 5 are not strictly required so I like the idea of adding them in follow-ups in parallel. That way we can start iterating on other areas with this as the basis. -- 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]
