DeltaCommits

Commit changes to a specified Delta table. The server has a limit defined in config on how many unbackfilled commits it can hold. Clients are expected to do active backfill of the commit after committing to UC. So in most cases the number of unbackfilled commits should be close to zero or one. But if clients misbehave and unbackfilled commits accumulate beyond the limit, server will reject further commits until more backfill is done. Replaying an already-accepted commit (same version and file-name) is an idempotent no-op that returns 200, so a client that lost the response can safely resend. WARNING: This API is experimental and may change in future versions.

Changed on
post/delta/preview/commits

Request

  • Base URL
    http://localhost:8080/api/2.1/unity-catalog
  • Auth
    none declared

Request body

table_idstring required

The ID of the table to commit to. This ID uniquely identifies a table.

table_uristring required

The URI of the storage location of the table. If the table_id exists but the table_uri is different from the one previously registered (e.g., if the client moved the table), the request will fail. Example: s3://bucket-name/tables/some-table-id

latest_backfilled_versioninteger

The highest version of the commits that have been backfilled for this table; meaning UC no longer needs to keep track of commits of versions <= this version.

Response

Successful response

DeltaCommitResponse required

The response for the Delta commit action

Changes