Skip to main content
PATCH
Update CDC ClickPipes scaling
Update scaling settings for database ClickPipes (PostgreSQL, MySQL, MongoDB, BigQuery). The infrastructure is shared between all database ClickPipes in the service, both for initial load and CDC. Scaling settings may take a few minutes to fully propagate. For billing purposes, 2 CPU cores and 8 GB of RAM correspond to one compute unit. If your organization tier changes, database ClickPipes will be rescaled appropriately. Note: For Kafka, Kinesis, and object storage pipes (S3, GCS, Azure Blob), see Get ClickPipe. This endpoint becomes available once at least one database ClickPipe was provisioned.

Autorizaciones

Authorization
string
header
requerido

Use key ID and key secret obtained in ClickHouse Cloud console: https://clickhouse.com/docs/cloud/manage/openapi

Parámetros de ruta

organizationId
string<uuid>
requerido

ID of the organization that owns the service.

serviceId
string<uuid>
requerido

ID of the service that owns the ClickPipe.

Cuerpo

application/json
replicaCpuMillicores
integer

CPU in millicores for DB ClickPipes.

Rango requerido: 1000 <= x <= 32000Debe ser un múltiplo de 1000
Ejemplo:

2000

replicaMemoryGb
number

Memory in GiB for DB ClickPipes. Must be 4× the CPU core count.

Rango requerido: 4 <= x <= 128Debe ser un múltiplo de 4
Ejemplo:

8

Respuesta

Successful response

status
number

HTTP status code.

Ejemplo:

200

requestId
string<uuid>

Unique id assigned to every request. UUIDv4

result
object
Última modificación el 24 de julio de 2026