Skip to main content
POST
Start a Databricks Metric View publication run
Converts the configured Cube views from the deployment’s latest successful build and creates or replaces each one’s managed Databricks Metric View. Views publish independently: one that is incompatible, fails Databricks validation, or whose destination belongs to another integration keeps its last good definition and does not stop the others, and a view whose definition is unchanged is skipped without a Databricks write. One run per integration at a time; a second start while one is active returns 409. Requires a Databricks datasource, enabled publication settings, and SchemaUpdate access. This is currently in preview — reach out to the Cube support team to activate it for your account.

Authorizations

Authorization
string
header
required

Token authentication. Send Authorization: Bearer <YOUR_TOKEN>.

Path Parameters

deploymentId
integer
required
dataSourceName
string
required

Body

application/json

StartDatabricksMetricViewSyncInput

configurationVersion
integer
required

The configurationVersion returned by GET. A run is refused when settings changed after they were loaded, so a publish always uses the configuration the caller saw.

Required range: x >= 1
idempotencyKey
string<uuid> | null

Optional idempotency key. Repeating a start with the same key returns the original run instead of publishing twice; omit it and every call starts a new run.

Response

202 - application/json
buildJobId
integer
required

The build whose deployed model this run publishes.

dataSourceName
string
required
deploymentId
integer
required
integrationPublicId
string
required
reused
boolean
required

True when an idempotent retry returned an existing run.

runId
string
required
statusUrl
string
required
commit
string | null