- HTTP request
- Path parameters
- Query parameters
- Request body
- Response body
- Authorization Scopes
- Try it!
Creates an assignment object which allows the given project to submit jobs of a certain type using slots from the specified reservation.
Currently a resource (project, folder, organization) can only have one assignment per each (jobType, location) combination, and that reservation will be used for all jobs of the matching type.
Different assignments can be created on different levels of the projects, folders or organization hierarchy. During query execution, the assignment is looked up at the project, folder and organization levels in that order. The first assignment found is applied to the query.
When creating assignments, it does not matter if other assignments exist at higher levels.
- The organization
organizationAcontains two projects,
- Assignments for all three entities (
project2) could all be created and mapped to the same or different reservations.
"None" assignments represent an absence of the assignment. Projects assigned to None use on-demand pricing. To create a "None" assignment, use "none" as a reservationId in the parent. Example parent:
google.rpc.Code.PERMISSION_DENIED if user does not have 'bigquery.admin' permissions on the project using the reservation and the project that owns this reservation.
google.rpc.Code.INVALID_ARGUMENT when location of the assignment does not match location of the reservation.
The URL uses gRPC Transcoding syntax.
Required. The parent resource name of the assignment E.g.
Authorization requires the following IAM permission on the specified resource
The optional assignment ID. Assignment name will be generated automatically if this field is empty. This field must only contain lower case alphanumeric characters or dash. Max length is 64 characters.
The request body contains an instance of
If successful, the response body contains a newly created instance of
Requires one of the following OAuth scopes:
For more information, see the Authentication Overview.