Hi Vignesh, Thanks for raising this!
Carrying over my point from the PR: When polaris.iceberg-metrics.reporting.type=persisting, the user has explicitly chosen to persist metrics. Since Polaris selects only one reporter, I think a persistence failure should fail the metrics request so the client can observe it. The Iceberg Java client already catches and logs metrics-endpoint errors. Could we remove both catches and let persistence errors propagate? I'm open to different thoughts on this. Best, Yufei On Thu, Oct 22, 2026 at 11:11 AM vignesh a <[email protected]> wrote: > Hi all, > > PR #5395 [1] is about to land, and I wanted to flag it here because it > changes REST behaviour compared to today. > > With this change, POST .../metrics no longer returns a 500 when the > persisting reporter's DB write fails. The error is logged and the > report is dropped. Errors from other reporters still propagate through > the handler as before, and authorization is unchanged. > > Iceberg Java already ignores errors from the metrics endpoint. This > change keeps a broken metrics store from showing up as catalog 5xx > errors. > > Thoughts welcome, especially if anyone relies on the current 500 > behaviour. > > Thanks, > Vignesh > > [1] https://github.com/apache/polaris/pull/5395 >
