personal_compute

Creates, updates, deletes, gets or lists a personal_compute resource.

Overview

Name	personal_compute
Type	Resource
Id	databricks_workspace.settings.personal_compute

Fields

The following fields are returned by SELECT queries:

get

Name	Datatype	Description
setting_name	string	Name of the corresponding setting. This field is populated in the response, but it will not be respected even if it's set in the request body. The setting name in the path parameter will be respected instead. Setting name is required to be 'default' if the setting only has one instance per workspace.
etag	string	etag used for versioning. The response is at least as fresh as the eTag provided. This is used for optimistic concurrency control as a way to help prevent simultaneous writes of a setting overwriting each other. It is strongly suggested that systems make use of the etag in the read -> update pattern to perform setting updates in order to avoid race conditions. That is, get an etag from a GET request, and pass it with the PATCH request to identify the setting version you are updating.
▶personal_compute	object

Methods

The following methods are available for this resource:

Name	Accessible by	Required Params	Optional Params	Description
get	select	account_id, deployment_name	etag	Gets the value of the Personal Compute setting.
update	update	account_id, deployment_name, allow_missing, setting, field_mask		Updates the value of the Personal Compute setting.
delete	delete	account_id, deployment_name	etag	Reverts back the Personal Compute setting value to default (ON)

Parameters

Parameters can be passed in the WHERE clause of a query. Check the Methods section to see which parameters are required or optional for each operation.

Name	Datatype	Description
account_id	string
deployment_name	string	The Databricks Workspace Deployment Name (default: dbc-abcd0123-a1bc)
etag	string	etag used for versioning. The response is at least as fresh as the eTag provided. This is used for optimistic concurrency control as a way to help prevent simultaneous writes of a setting overwriting each other. It is strongly suggested that systems make use of the etag in the read -> delete pattern to perform setting deletions in order to avoid race conditions. That is, get an etag from a GET request, and pass it with the DELETE request to identify the rule set version you are deleting.

SELECT examples

get

Gets the value of the Personal Compute setting.

SELECT
setting_name,
etag,
personal_compute
FROM databricks_workspace.settings.personal_compute
WHERE account_id = '{{ account_id }}' -- required
AND deployment_name = '{{ deployment_name }}' -- required
AND etag = '{{ etag }}'
;

UPDATE examples

update

Updates the value of the Personal Compute setting.

UPDATE databricks_workspace.settings.personal_compute
SET 
allow_missing = {{ allow_missing }},
setting = '{{ setting }}',
field_mask = '{{ field_mask }}'
WHERE 
account_id = '{{ account_id }}' --required
AND deployment_name = '{{ deployment_name }}' --required
AND allow_missing = {{ allow_missing }} --required
AND setting = '{{ setting }}' --required
AND field_mask = '{{ field_mask }}' --required
RETURNING
setting_name,
etag,
personal_compute;

DELETE examples

delete

Reverts back the Personal Compute setting value to default (ON)

DELETE FROM databricks_workspace.settings.personal_compute
WHERE account_id = '{{ account_id }}' --required
AND deployment_name = '{{ deployment_name }}' --required
AND etag = '{{ etag }}'
;