Hi Yufei, Thanks for following up. I see the point: if Iceberg already ignores errors from the metrics POST, a Polaris 500 often won't fail the job, and it can still tell an operator that the persist failed.
What I'm trying to avoid is Polaris itself counting that as a catalog 5xx (in SLOs, or anything that treats POST .../metrics failures as the catalog being down) when an admin turns persisting on and the metrics table is unhealthy. We still log the failed write at WARN, so that signal stays on the server. If you'd rather keep the 500 for operator visibility, I'd like to understand that use case better. Thanks, Vignesh
