ClickHouse Cloud: Clickhouse Click Pipe Cdc Scaling Update

Update CDC ClickPipes scaling.

Tool ID: clickhouse_click_pipe_cdc_scaling_update

Run this action

Use the TypeScript SDK for a single call. Put ctx.tools.execute(...) inside a Play when the call should be durable, scheduled, or run across a CSV.

import { Deepline } from 'deepline';

const deepline = await Deepline.connect();
const result = await deepline.tools.execute(
  'clickhouse_click_pipe_cdc_scaling_update',
  {
    "organizationId": "123e4567-e89b-42d3-a456-426614174000",
    "serviceId": "123e4567-e89b-42d3-a456-426614174000"
  },
);

console.log(result.toolResponse.raw);

CLI

deepline tools execute clickhouse_click_pipe_cdc_scaling_update --input '{
  "organizationId": "123e4567-e89b-42d3-a456-426614174000",
  "serviceId": "123e4567-e89b-42d3-a456-426614174000"
}' --json

Example response

The SDK exposes this shape at result.toolResponse.raw. Values below are representative.

{
  "data": {
    "status": 123,
    "requestId": "123e4567-e89b-42d3-a456-426614174000",
    "result": {
      "replicaCpuMillicores": 1000,
      "replicaMemoryGb": 124
    }
  }
}

Use deepline tools get clickhouse_click_pipe_cdc_scaling_update --json for the latest machine-readable contract.

Input reference

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.

Name	Type	Required	Default	Details
`payload.organizationId`	`string`	Yes	—	ID of the organization that owns the service. Format: `uuid`.
`payload.serviceId`	`string`	Yes	—	ID of the service that owns the ClickPipe. Format: `uuid`.
`payload.replicaCpuMillicores`	`integer`	No	—	CPU in millicores for DB ClickPipes. Minimum: 1000. Maximum: 32000.
`payload.replicaMemoryGb`	`number`	No	—	Memory in GiB for DB ClickPipes. Must be 4× the CPU core count. Minimum: 4. Maximum: 128.

Output reference

Standard tool result payload.

Name	Type	Required	Default	Details
`result.data`	`object`	Yes	—	Provider response payload.
`result.data.status`	`number`	No	—	HTTP status code.
`result.data.requestId`	`string`	No	—	Unique id assigned to every request. UUIDv4 Format: `uuid`.
`result.data.result`	`object`	No	—	—
`result.data.result.replicaCpuMillicores`	`integer`	No	—	CPU in millicores for DB ClickPipes. Minimum: 1000. Maximum: 32000.
`result.data.result.replicaMemoryGb`	`number`	No	—	Memory in GiB for DB ClickPipes. Must be 4× the CPU core count. Minimum: 4. Maximum: 128.
`result.meta`	`object`	No	—	Additional response metadata (status, paging).

Deepline cost

Pricing model: fixed (per call).
Estimated Deepline credits: 0 per pricing unit.
Provider-native pricing may still exist outside Deepline credit billing.

Get started

Build and automate

Common workflows

Data and integrations

Reference

ClickHouse Cloud: Clickhouse Click Pipe Cdc Scaling Update

Run this action

CLI

Example response

Input reference

Output reference

Deepline cost

​Run this action

​CLI

​Example response

​Input reference

​Output reference

​Deepline cost

​Related documentation

Run this action

CLI

Example response

Input reference

Output reference

Deepline cost

Related documentation