kbendick edited a comment on pull request #3770: URL: https://github.com/apache/iceberg/pull/3770#issuecomment-1004309804
Thanks for the pending thoughts @jackye1995! I'll respond a bit, and then we'll keep these for later discussion as well (assuming there will be more discussion groups / follow up PRs etc) > 1. if it's better to have specific operation routes for non-RESTful operations Agreed. > 2. head table/namespace operation with response, if we do that what set of fields should be in the response So currently, there's no set of fields in the response for HEAD requests. That's what the response code and just the string `description` represents. Technically, HEAD requests are not supposed to have a response body. However, so many famous APIs do that I think we can add them in a follow up. > 3. if pagination of response is needed when there are too many metadata log or snapshots I had brought up pagination for one or two routes, but it was deemed as somewhat premature. I think eventually we will definitely need some kind of pagination for sure. > 4. progress tracking for table purge Will be coming in a follow up. > 5. drop namespace cascade That one is not currently implemented, but I agree. Once we finish implementing it, it should be easy to add in. We can start considering where to put it in the API here sooner. Probably as a query parameter I would think. -- 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]
