dimas-b commented on PR #4646: URL: https://github.com/apache/polaris/pull/4646#issuecomment-4693901204
None of the options are ideal :sweat_smile: We're effectively trying to work around an IRC spec problem, while allowing reasonable clients to recover from this kind of failure without having to make any Polaris-specific assumptions. As I commented on `dev`, from my POV 503 is the easiest to handle on the client side because it does not carry any implications about the state of the catalog. The server merely could not handle the request (from the client perspective). With 503, the [RFC](https://www.rfc-editor.org/info/rfc9110/#status.503) is pretty lenient towards servers. I do not think clients can assume any service-wise outage on receiving a 503 response from one particular request. As Polaris will not provide a `Retry-After` response header in this case, the client is free to retry at any time. -- 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]
