bharos commented on issue #10713: URL: https://github.com/apache/gravitino/issues/10713#issuecomment-4239891240
I think the approach from @mehakmeet makes sense — the warnings field for Gravitino REST API and X-Gravitino-Warning header for IRS is a clean separation. One thing to consider: current Iceberg REST clients (Trino, Spark, RESTSessionCatalog) parse only the response body and status code — they'll silently ignore custom headers. And the Gravitino Java/Python clients don't parse the warnings field today either. So in practice, the ownership failure will only be visible in server logs for now. Given that, should we also consider server-side resilience to make the failure less probable in the first place? (These are optional improvements that can be considered separately as well, not a blocker) - Inline retry with backoff — if setOwner fails, retry 2-3 times before giving up. Most transient EntityStore failures would self-heal without any client awareness needed. - Metric/audit — emit something like gravitino.ownership.set_failed so ops teams can monitor and alert, rather than relying on clients to parse warnings. -- 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]
