Cloud Spanner is a managed, mission-critical, globally consistent and scalable relational database service.

A session in the Cloud Spanner Adapter API.

Message sent by the client to the adapter.

Message sent by the adapter to the client.

The request for AddSplitPoints.

The response for AddSplitPoints.

AsymmetricAutoscalingOption specifies the scaling of replicas identified by the given selection.

Autoscaling configuration for an instance.

Overrides the top-level autoscaling configuration for the replicas identified by replica_selection. All fields in this message are optional. Any unspecified fields will use the corresponding values from the top-level autoscaling configuration.

The autoscaling limits for the instance. Users can define the minimum and maximum compute capacity allocated to the instance, and the autoscaler will only scale within that range. Users can either use nodes or processing units to specify the limits, but should use the same unit to set both the min_limit and max_limit.

The autoscaling targets for an instance.

A backup of a Cloud Spanner database.

Information about a backup.

Instance partition information for the backup.

BackupSchedule expresses the automated backup creation specification for a Spanner database.

Defines specifications of the backup schedule.

The request for BatchCreateSessions.

The response for BatchCreateSessions.

The request for BatchWrite.

The result of applying a batch of mutations.

The request for BeginTransaction.

Associates members, or principals, with a role.

Metadata type for the long-running operation returned by ChangeQuorum.

The request for ChangeQuorum.

Spanner Change Streams enable customers to capture and stream out changes to their Spanner databases in real-time. A change stream can be created with option partition_mode='IMMUTABLE_KEY_RANGE' or partition_mode='MUTABLE_KEY_RANGE'. This message is only used in Change Streams created with the option partition_mode='MUTABLE_KEY_RANGE'. Spanner automatically creates a special Table-Valued Function (TVF) along with each Change Streams. The function provides access to the change stream's records. The function is named READ_ (where is the name of the change stream), and it returns a table with only one column called ChangeRecord.

Metadata associated with a parent-child relationship appearing in a PlanNode.

Metadata for a column.

The request for Commit.

The response for Commit.

Additional statistics about a commit.

A message representing context for a KeyRangeInfo, including a label, value, unit, and severity.

Encryption configuration for the copied backup.

Metadata type for the operation returned by CopyBackup.

The request for CopyBackup.

Encryption configuration for the backup to create.

Metadata type for the operation returned by CreateBackup.

Metadata type for the operation returned by CreateDatabase.

The request for CreateDatabase.

Metadata type for the operation returned by CreateInstanceConfig.

The request for CreateInstanceConfig.

Metadata type for the operation returned by CreateInstance.

Metadata type for the operation returned by CreateInstancePartition.

The request for CreateInstancePartition.

The request for CreateInstance.

The request for CreateSession.

Defines the root interface for all clients that generate credentials for calling Google APIs. All clients should implement this interface.

CrontabSpec can be used to specify the version time and frequency at which the backup is created.

A Cloud Spanner database.

The configuration for each database in the target instance configuration.

A Cloud Spanner database role.

A data change record contains a set of changes to a table with the same modification type (insert, update, or delete) committed at the same commit timestamp in one change stream partition for the same transaction. Multiple data change records can be returned for the same transaction across multiple change stream partitions.

Action information extracted from a DDL statement. This proto is used to display the brief info of the DDL statement for the operation UpdateDatabaseDdl.

Arguments to delete operations.

A message representing a derived metric.

A message representing the key visualizer diagnostic messages.

The DirectedReadOptions can be used to indicate which replicas or regions should be used for non-transactional reads or queries. DirectedReadOptions can only be specified for a read-only transaction, otherwise the API returns an INVALID_ARGUMENT error.

Message type for a dual-region quorum. Currently this type has no options.

A generic empty message that you can re-use to avoid defining duplicated empty messages in your APIs. A typical example is to use it as the request or the response type of an API method. For instance: service Foo { rpc Bar(google.protobuf.Empty) returns (google.protobuf.Empty); }

Encryption configuration for a Cloud Spanner database.

Encryption information for a Cloud Spanner database or backup.

An ExcludeReplicas contains a repeated set of ReplicaSelection that should be excluded from serving requests.

The request for ExecuteBatchDml.

The response for ExecuteBatchDml. Contains a list of ResultSet messages, one for each DML statement that has successfully executed, in the same order as the statements in the request. If a statement fails, the status in the response body identifies the cause of the failure. To check for DML statements that failed, use the following approach: 1. Check the status in the response message. The google.rpc.Code enum value OK indicates that all statements were executed successfully. 2. If the status was not OK, check the number of result sets in the response. If the response contains N ResultSet messages, then statement N+1 in the request failed. Example 1: * Request: 5 DML statements, all executed successfully. * Response: 5 ResultSet messages, with the status OK. Example 2: * Request: 5 DML statements. The third statement has a syntax error. * Response: 2 ResultSet messages, and a syntax error (INVALID_ARGUMENT) status. The number of ResultSet messages indicates that the third statement failed, and the fourth and fifth statements were not executed.

The request for ExecuteSql and ExecuteStreamingSql.

Represents a textual expression in the Common Expression Language (CEL) syntax. CEL is a C-like expression language. The syntax and semantics of CEL are documented at https://github.com/google/cel-spec. Example (Comparison): title: "Summary size limit" description: "Determines if a summary is less than 100 chars" expression: "document.summary.size() < 100" Example (Equality): title: "Requestor is owner" description: "Determines if requestor is the document owner" expression: "document.owner == request.auth.claims.email" Example (Logic): title: "Public documents" description: "Determine whether the document should be publicly visible" expression: "document.type != 'private' && document.type != 'internal'" Example (Data Manipulation): title: "Notification string" description: "Create a notification string with a timestamp." expression: "'New message received at ' + string(document.create_time)" The exact variables and functions that may be referenced within an expression are determined by the service that evaluates it. See the service documentation for additional information.

Message representing a single field of a struct.

Free instance specific metadata that is kept even after an instance has been upgraded for tracking purposes.

The specification for full backups. A full backup stores the entire contents of the database at a given version time.

The response for GetDatabaseDdl.

Request message for GetIamPolicy method.

Encapsulates settings provided to GetIamPolicy.

A heartbeat record is returned as a progress indicator, when there are no data changes or any other partition record types in the change stream partition.

An IncludeReplicas contains a repeated set of ReplicaSelection which indicates the order in which replicas should be considered.

The specification for incremental backup chains. An incremental backup stores the delta of changes between a previous backup and the database contents at a given version time. An incremental backup chain consists of a full backup and zero or more successive incremental backups. The first backup created for an incremental backup chain is always a full backup.

Recommendation to add new indexes to run queries more efficiently.

A message representing a (sparse) collection of hot keys for specific key buckets.

A message representing a (sparse) collection of KeyRangeInfos for specific key buckets.

An isolated set of Cloud Spanner resources on which databases can be hosted.

A possible configuration for a Cloud Spanner instance. Configurations define the geographic placement of nodes and their replication.

Encryption configuration for a Cloud Spanner database.

Encapsulates progress related information for a Cloud Spanner long running instance operations.

An isolated set of Cloud Spanner resources that databases can define placements on.

ReplicaSelection identifies replicas with common properties.

A split key.

KeyRange represents a range of rows in a table or index. A range has a start key and an end key. These keys can be open or closed, indicating if the range includes rows with that key. Keys are represented by lists, where the ith value in the list corresponds to the ith component of the table or index primary key. Individual values are encoded as described here. For example, consider the following table definition: CREATE TABLE UserEvents ( UserName STRING(MAX), EventDate STRING(10) ) PRIMARY KEY(UserName, EventDate); The following keys name rows in this table: "Bob", "2014-09-23" Since the UserEvents table's PRIMARY KEY clause names two columns, each UserEvents key has two elements; the first is the UserName, and the second is the EventDate. Key ranges with multiple components are interpreted lexicographically by component using the table or index key's declared sort order. For example, the following range returns all events for user "Bob" that occurred in the year 2015: "start_closed": ["Bob", "2015-01-01"] "end_closed": ["Bob", "2015-12-31"] Start and end keys can omit trailing key components. This affects the inclusion and exclusion of rows that exactly match the provided key components: if the key is closed, then rows that exactly match the provided components are included; if the key is open, then rows that exactly match are not included. For example, the following range includes all events for "Bob" that occurred during and after the year 2000: "start_closed": ["Bob", "2000-01-01"] "end_closed": ["Bob"] The next example retrieves all events for "Bob": "start_closed": ["Bob"] "end_closed": ["Bob"] To retrieve events before the year 2000: "start_closed": ["Bob"] "end_open": ["Bob", "2000-01-01"] The following range includes all rows in the table: "start_closed": [] "end_closed": [] This range returns all users whose UserName begins with any character from A to C: "start_closed": ["A"] "end_open": ["D"] This range returns all users whose UserName begins with B: "start_closed": ["B"] "end_open": ["C"] Key ranges honor column sort order. For example, suppose a table is defined as follows: CREATE TABLE DescendingSortedTable { Key INT64, ... ) PRIMARY KEY(Key DESC); The following range retrieves all rows with key values between 1 and 100 inclusive: "start_closed": ["100"] "end_closed": ["1"] Note that 100 is passed as the start, and 1 is passed as the end, because Key is a descending column in the schema.

A message representing information for a key range (possibly one key).

A message representing a list of specific information for multiple key ranges.

KeySet defines a collection of Cloud Spanner keys and/or key ranges. All the keys are expected to be in the same table or index. The keys need not be sorted in any particular way. If the same key is specified multiple times in the set (for example if two ranges, two keys, or a key and a range overlap), Cloud Spanner behaves as if the key were only specified once.

The response for ListBackupOperations.

The response for ListBackupSchedules.

The response for ListBackups.

The response for ListDatabaseOperations.

The response for ListDatabaseRoles.

The response for ListDatabases.

The response for ListInstanceConfigOperations.

The response for ListInstanceConfigs.

The response for ListInstancePartitionOperations.

The response for ListInstancePartitions.

The response for ListInstances.

The response message for Operations.ListOperations.

Response method from the ListScans method.

The response for ListSessions.

A message representing a user-facing string whose value may need to be translated before being displayed.

A message representing the actual monitoring data, values for each key bucket over time, of a metric.

A message representing a matrix of floats.

A message representing a row of a matrix of floats.

A mod describes all data changes in a watched table row.

Returns the value and associated metadata for a particular field of the Mod.

Describes move-in of the key ranges into the change stream partition identified by partition_token. To maintain processing the changes for a particular key in timestamp order, the query processing the change stream partition identified by partition_token should not advance beyond the partition event record commit timestamp until the queries processing the source change stream partitions have processed all change stream records with timestamps <= the partition event record commit timestamp.

The request for MoveInstance.

Describes move-out of the key ranges out of the change stream partition identified by partition_token. To maintain processing the changes for a particular key in timestamp order, the query processing the MoveOutEvent in the partition identified by partition_token should inform the queries processing the destination partitions that they can unblock and proceed processing records past the commit_timestamp.

When a read-write transaction is executed on a multiplexed session, this precommit token is sent back to the client as a part of the Transaction message in the BeginTransaction response and also as a part of the ResultSet and PartialResultSet responses.

A modification to one or more Cloud Spanner rows. Mutations can be applied to a Cloud Spanner database by sending them in a Commit call.

A group of mutations to be committed together. Related mutations should be placed in a group. For example, two mutations inserting rows with the same primary key prefix in both parent and child tables are related.

This resource represents a long-running operation that is the result of a network API call.

Encapsulates progress related information for a Cloud Spanner long running operation.

Metadata type for the long-running operation used to track the progress of optimizations performed on a newly restored database. This long-running operation is automatically created by the system after the successful completion of a database restore, and cannot be cancelled.

Partial results from a streaming read or SQL query. Streaming reads and SQL queries better tolerate large result sets, large rows, and large values, but are a little trickier to consume.

Information returned for each partition returned in a PartitionResponse.

Message type to initiate a Partitioned DML transaction.

A partition end record serves as a notification that the client should stop reading the partition. No further records are expected to be retrieved on it.

A partition event record describes key range changes for a change stream partition. The changes to a row defined by its primary key can be captured in one change stream partition for a specific time range, and then be captured in a different change stream partition for a different time range. This movement of key ranges across change stream partitions is a reflection of activities, such as Spanner's dynamic splitting and load balancing, etc. Processing this event is needed if users want to guarantee processing of the changes for any key in timestamp order. If time ordered processing of changes for a primary key is not needed, this event can be ignored. To guarantee time ordered processing for each primary key, if the event describes move-ins, the reader of this partition needs to wait until the readers of the source partitions have processed all records with timestamps <= this PartitionEventRecord.commit_timestamp, before advancing beyond this PartitionEventRecord. If the event describes move-outs, the reader can notify the readers of the destination partitions that they can continue processing.

Options for a PartitionQueryRequest and PartitionReadRequest.

The request for PartitionQuery

The request for PartitionRead

The response for PartitionQuery or PartitionRead

A partition start record serves as a notification that the client should schedule the partitions to be queried. PartitionStartRecord returns information about one or more partitions.

Node information for nodes appearing in a QueryPlan.plan_nodes.

An Identity and Access Management (IAM) policy, which specifies access controls for Google Cloud resources. A Policy is a collection of bindings. A binding binds one or more members, or principals, to a single role. Principals can be user accounts, service accounts, Google groups, and domains (such as G Suite). A role is a named list of permissions; each role can be an IAM predefined role or a user-created custom role. For some types of Google Cloud resources, a binding can also specify a condition, which is a logical expression that allows access to a resource only if the expression evaluates to true. A condition can add constraints based on attributes of the request, the resource, or both. To learn which resources support conditions in their IAM policies, see the IAM documentation. JSON example: { "bindings": [ { "role": "roles/resourcemanager.organizationAdmin", "members": [ "user:mike@example.com", "group:admins@example.com", "domain:google.com", "serviceAccount:my-project-id@appspot.gserviceaccount.com" ] }, { "role": "roles/resourcemanager.organizationViewer", "members": [ "user:eve@example.com" ], "condition": { "title": "expirable access", "description": "Does not grant access after Sep 2020", "expression": "request.time < timestamp('2020-10-01T00:00:00.000Z')", } } ], "etag": "BwWWja0YfJA=", "version": 3 } YAML example: ``` bindings: - members:

• user:mike@example.com - group:admins@example.com - domain:google.com - serviceAccount:my-project-id@appspot.gserviceaccount.com role: roles/resourcemanager.organizationAdmin - members: - user:eve@example.com role: roles/resourcemanager.organizationViewer condition: title: expirable access description: Does not grant access after Sep 2020 expression: request.time < timestamp('2020-10-01T00:00:00.000Z') etag: BwWWja0YfJA= version: 3 ``` For a description of IAM and its features, see the IAM documentation.

A message representing a key prefix node in the key prefix hierarchy. for eg. Bigtable keyspaces are lexicographically ordered mappings of keys to values. Keys often have a shared prefix structure where users use the keys to organize data. Eg ///employee In this case Keysight will possibly use one node for a company and reuse it for all employees that fall under the company. Doing so improves legibility in the UI.

Additional options for Spanner#projectsInstanceConfigOperationsList.

Additional options for Spanner#projectsInstanceConfigsDelete.

Additional options for Spanner#projectsInstanceConfigsList.

Additional options for Spanner#projectsInstanceConfigsOperationsList.

Additional options for Spanner#projectsInstanceConfigsSsdCachesOperationsList.

Additional options for Spanner#projectsInstancesBackupOperationsList.

Additional options for Spanner#projectsInstancesBackupsCreate.

Additional options for Spanner#projectsInstancesBackupsList.

Additional options for Spanner#projectsInstancesBackupsOperationsList.

Additional options for Spanner#projectsInstancesBackupsPatch.

Additional options for Spanner#projectsInstancesDatabaseOperationsList.

Additional options for Spanner#projectsInstancesDatabasesBackupSchedulesCreate.

Additional options for Spanner#projectsInstancesDatabasesBackupSchedulesList.

Additional options for Spanner#projectsInstancesDatabasesBackupSchedulesPatch.

Additional options for Spanner#projectsInstancesDatabasesDatabaseRolesList.

Additional options for Spanner#projectsInstancesDatabasesGetScans.

Additional options for Spanner#projectsInstancesDatabasesList.

Additional options for Spanner#projectsInstancesDatabasesOperationsList.

Additional options for Spanner#projectsInstancesDatabasesPatch.

Additional options for Spanner#projectsInstancesDatabasesSessionsList.

Additional options for Spanner#projectsInstancesGet.

Additional options for Spanner#projectsInstancesInstancePartitionOperationsList.

Additional options for Spanner#projectsInstancesInstancePartitionsDelete.

Additional options for Spanner#projectsInstancesInstancePartitionsList.

Additional options for Spanner#projectsInstancesInstancePartitionsOperationsList.

Additional options for Spanner#projectsInstancesList.

Additional options for Spanner#projectsInstancesOperationsList.

Output of query advisor analysis.

Query optimizer configuration.

Contains an ordered list of nodes appearing in the query plan.

Information about the dual-region quorum.

Information about the database quorum type. This only applies to dual-region instance configs.

Message type to initiate a read-only transaction.

The request for Read and StreamingRead.

Message type to initiate a read-write transaction. Currently this transaction type has no options.

ReplicaComputeCapacity describes the amount of server resources that are allocated to each replica identified by the replica selection.

The directed read replica selector. Callers must provide one or more of the following fields for replica selection: * location - The location must be one of the regions within the multi-region configuration of your database. * type - The type of the replica. Some examples of using replica_selectors are: * location:us-east1 --> The "us-east1" replica(s) of any available type is used to process the request. * type:READ_ONLY --> The "READ_ONLY" type replica(s) in the nearest available location are used to process the request. * location:us-east1 type:READ_ONLY --> The "READ_ONLY" type replica(s) in location "us-east1" is used to process the request.

Common request options for various APIs.

Encryption configuration for the restored database.

Metadata type for the long-running operation returned by RestoreDatabase.

The request for RestoreDatabase.

Information about the database restore.

Results from Read or ExecuteSql.

Metadata about a ResultSet or PartialResultSet.

Additional statistics about a ResultSet or PartialResultSet.

The request for Rollback.

Scan is a structure which describes Cloud Key Visualizer scan information.

ScanData contains Cloud Key Visualizer scan data used by the caller to construct a visualization.

Additional options for Spanner#scansList.

A session in the Cloud Spanner API.

Request message for SetIamPolicy method.

Condensed representation of a node and its subtree. Only present for SCALAR PlanNode(s).

Message type for a single-region quorum.

The split points of a table or an index.

A single DML statement.

The Status type defines a logical error model that is suitable for different programming environments, including REST APIs and RPC APIs. It is used by gRPC. Each Status message contains three pieces of data: error code, error message, and error details. You can find out more about this error model and how to work with it in the API Design Guide.

StructType defines the fields of a STRUCT type.

Request message for TestIamPermissions method.

Response message for TestIamPermissions method.

A transaction.

Options to use for transactions.

This message is used to select the transaction in which a Read or ExecuteSql call runs. See TransactionOptions for more information about transactions.

Type indicates the type of a Cloud Spanner value, as might be stored in a table cell or returned from an SQL query.

Metadata type for the operation returned by UpdateDatabaseDdl.

Enqueues the given DDL statements to be applied, in order but not necessarily all at once, to the database schema at some point (or points) in the future. The server checks that the statements are executable (syntactically valid, name tables that exist, etc.) before enqueueing them, but they may still fail upon later execution (e.g., if a statement from another batch of statements is applied first and it conflicts in some way, or if there is some data-related problem like a NULL value in a column to which NOT NULL would be added). If a statement fails, all subsequent statements in the batch are automatically cancelled. Each batch of statements is assigned a name which can be used with the Operations API to monitor progress. See the operation_id field for more details.

Metadata type for the operation returned by UpdateDatabase.

The request for UpdateDatabase.

Metadata type for the operation returned by UpdateInstanceConfig.

The request for UpdateInstanceConfig.

Metadata type for the operation returned by UpdateInstance.

Metadata type for the operation returned by UpdateInstancePartition.

The request for UpdateInstancePartition.

The request for UpdateInstance.

Arguments to insert, update, insert_or_update, and replace operations.