cancel
Showing results for 
Search instead for 
Did you mean: 
Data Engineering
Join discussions on data engineering best practices, architectures, and optimization strategies within the Databricks Community. Exchange insights and solutions with fellow data engineers.
cancel
Showing results for 
Search instead for 
Did you mean: 

What is the possible cause in calling the dataricks Job permission API

Lloydy
New Contributor
 
PATCH /api/2.0/permissions/jobs/{job_id}
 
 
{
    "error_code": "INVALID_PARAMETER_VALUE",
    "message": "Owner permissions cannot be modified via an update / PATCH request if the endpoint does not have a valid owner. Please use a set / PUT request instead."
}
1 REPLY 1

Vidhi_Khaitan
Databricks Employee
Databricks Employee

Hi team,
This seems to be an expected behaviour.

The PATCH endpoint for updating job permissions is designed for incremental modifications of existing permissions. However, modifying owner permissions is restricted unless a valid owner already exists in the endpoint. This guard ensures that owner-specific permissions cannot be partially or improperly modified, preserving data integrity and access control consistency.

To address the issue, you should use the PUT /api/2.0/permissions/jobs/{job_id} endpoint instead of PATCH for owner-level modifications. The PUT operation replaces the entire permission set of the targeted job, thereby allowing changes to ownership attributes

Join Us as a Local Community Builder!

Passionate about hosting events and connecting people? Help us grow a vibrant local community—sign up today to get started!

Sign Up Now