tiering

Apply one tiering decision

Changed on

Starts one supervised executor attempt for the partition's current actionable verdict. The request must include nodeId and the stateToken observed from /tiering/plan; stale tokens return 409. The leg runs detached from the request: the 202 response acknowledges admission with outcome "started", the leg is visible in /tiering/status inFlight until it converges, and its completion lands in /tiering/history.

post/tiering/tables/{database}/{table}/partitions/{partitionId}/apply

Request

  • Base URL: /api/v1 (relative, and the document was published on a file host, not at the API’s origin)
  • URL: /api/v1/tiering/tables/{database}/{table}/partitions/{partitionId}/apply
  • Auth: none declared

Path parameters

databasestring required
Example:movoor_dev

ClickHouse database name.

tablestring required
Example:test_generic_network_month_local

ClickHouse table name.

partitionIdstring required
Example:d82d64de29c8683be4aad2f0fd38d74e

ClickHouse partition_id verbatim.

Query parameters

nodeIdstring required
Example:shard1-replica1

Movoor configured node id. Tiering actions are node-local.

Request body

stateTokenstring required

Response

Apply admitted; the leg runs in the background.

Example response

{
  "item": {
    "outcome": "success",
    "bytes": "104"
  }
}

Changes