[I] Add idempotency support for createTableStaged [polaris]

["huaxingao (via GitHub)" <gi...@apache.org>]

huaxingao opened a new issue, #4200:
URL: https://github.com/apache/polaris/issues/4200

   ### Is your feature request related to a problem? Please describe.
   
   The handler-level idempotency implementation defers idempotency support for the createTableStaged endpoint.
   Staged tables are not persisted to the catalog, so the method can safely re-run on retry. The computed location is deterministic (based on namespace location + table name). The only differences on re-run are cosmetic (created-at timestamp and metadata UUID).
   Dedicated idempotency support may still be desirable for consistency. Options include skipping idempotency entirely (since re-run is safe) or storing the location in the idempotency record to replay via buildLoadTableResponseWithDelegationCredentials.
   
   
   ### Describe the solution you'd like
   
   _No response_
   
   ### Describe alternatives you've considered
   
   _No response_
   
   ### Additional context
   
   _No response_


-- 
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: issues-unsubscribe@polaris.apache.org.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org

Re: [I] Add idempotency support for createTableStaged [polaris]

["github-actions[bot] (via GitHub)" <gi...@apache.org>]

github-actions[bot] commented on issue #4200:
URL: https://github.com/apache/polaris/issues/4200#issuecomment-4456309755

   This issue is stale because it has been open 30 days with no activity. Remove stale label or comment if you think it's still relevant.


-- 
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: issues-unsubscribe@polaris.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org

Re: [I] Add idempotency support for createTableStaged [polaris]

["github-actions[bot] (via GitHub)" <gi...@apache.org>]

github-actions[bot] commented on issue #4200:
URL: https://github.com/apache/polaris/issues/4200#issuecomment-4703959512

   This issue is stale because it has been open 30 days with no activity. Remove stale label or comment if you think it's still relevant.


-- 
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: issues-unsubscribe@polaris.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org

Re: [I] Add idempotency support for createTableStaged [polaris]

["hemasrishalini (via GitHub)" <gi...@apache.org>]

hemasrishalini commented on issue #4200:
URL: https://github.com/apache/polaris/issues/4200#issuecomment-4456453748

   Hi @huaxingao, I’ve been looking into the staged table creation flow in `IcebergCatalogHandler`.
   
   From what I understand, `createTableStaged()` currently does not persist the table and retries are mostly safe, with differences mainly around generated metadata values (for example timestamps/UUIDs).
   
   Before I start implementing changes, I wanted to clarify the preferred direction:
   
   * should we explicitly add deterministic/idempotent replay behavior for staged creates, or
   * should we instead document/handle staged create as safely retryable without dedicated persistence of idempotency state?
   
   I’m happy to work on either approach depending on the intended behavior.
   


-- 
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: issues-unsubscribe@polaris.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org