laserninja opened a new issue, #12048: URL: https://github.com/apache/gravitino/issues/12048
## Describe the proposal The Iceberg REST spec defines an optional `Idempotency-Key` header (UUIDv7) on mutation endpoints. When present, the server must return the original response for replayed keys instead of re-executing the operation, preventing duplicate side-effects from client retries. This epic covers the full implementation of idempotency support in Gravitino's Iceberg REST server, including multi-node consistency. The design accounts for: - **Multi-node deployments**: Retries may hit different nodes behind a load balancer - **Node failure resilience**: Cached responses must survive node crashes - **Configurable storage backends**: In-memory (single-node/dev) and database-backed (production) - **Spec compliance**: `idempotency-key-lifetime` advertised in `GET /v1/config` Reference: [apache/polaris#3205](https://github.com/apache/polaris/pull/3205) (database-backed IdempotencyStore) Supersedes #10683. ## Task list - [ ] Design document: Idempotency-Key support (multi-node) - [ ] IdempotencyStore SPI interface and in-memory implementation - [ ] JDBC-backed IdempotencyStore using Gravitino's relational backend - [ ] Header handling, replay logic, and endpoint integration - [ ] Advertise idempotency-key-lifetime in GET /v1/config - [ ] Unit and integration tests -- 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]
