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

Lloydy — Tue, 25 Feb 2025 16:35:35 GMT

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."

}

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

Vidhi_Khaitan — Tue, 13 May 2025 09:35:16 GMT

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

topic What is the possible cause in calling the dataricks Job permission API in Data Engineering

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

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