lasdf1234 opened a new issue, #14358: URL: https://github.com/apache/gravitino/issues/14358
### What would you like to be improved? `table_snapshot_metrics` currently uses a unique constraint on `(table_id, policy_id, snapshot_id)`. When S0 and S1 share the same Iceberg snapshot, the second metrics insert is treated as idempotent and skipped, so S1 metrics are lost. ### How should we improve? - Use `metrics_id` as the primary key - Drop the unique constraint on `(table_id, policy_id, snapshot_id)` - Point action before/after to `before_metrics_id` / `after_metrics_id` - Keep drift detection on the Spark job side Related PR: #14357 -- 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]
