Cloud Spanner API (spanner:v1)


1 new method


  • spanner.projects.instances.databases.sessions.batchWrite

      Path: v1/{+session}:batchWrite

      Flat Path: v1/projects/{projectsId}/instances/{instancesId}/databases/{databasesId}/sessions/{sessionsId}:batchWrite

      HTTP Method: POST



          Description: Required. The session in which the batch request is to be run.

          Pattern: ^projects/[^/]+/instances/[^/]+/databases/[^/]+/sessions/[^/]+$

          Location: path

          Required: Yes

          Type: string

      Parameter Order: session


    • Description: Batches the supplied mutation groups in a collection of efficient transactions. All mutations in a group are committed atomically. However, mutations across groups can be committed non-atomically in an unspecified order and thus, they must be independent of each other. Partial failure is possible, i.e., some groups may have been committed successfully, while some may have failed. The results of individual batches are streamed into the response as the batches are applied. BatchWrite requests are not replay protected, meaning that each mutation group may be applied more than once. Replays of non-idempotent mutations may have undesirable effects. For example, replays of an insert mutation may produce an already exists error or result in additional rows if using generated or commit timestamp-based keys. We recommend structuring your mutation groups to be idempotent to avoid this issue.