google-api-python-client 2.174.0__py3-none-any.whl → 2.176.0__py3-none-any.whl

googleapiclient/discovery_cache/documents/spanner.v1.json

@@ -3406,7 +3406,7 @@
 }
 }
 },
-"revision": "20250523",
+"revision": "20250625",
 "rootUrl": "https://spanner.googleapis.com/",
 "schemas": {
 "AdaptMessageRequest": {
@@ -3966,6 +3966,33 @@
 },
 "type": "object"
 },
+"ChangeStreamRecord": {
+"description": "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.",
+"id": "ChangeStreamRecord",
+"properties": {
+"dataChangeRecord": {
+"$ref": "DataChangeRecord",
+"description": "Data change record describing a data change for a change stream partition."
+},
+"heartbeatRecord": {
+"$ref": "HeartbeatRecord",
+"description": "Heartbeat record describing a heartbeat for a change stream partition."
+},
+"partitionEndRecord": {
+"$ref": "PartitionEndRecord",
+"description": "Partition end record describing a terminated change stream partition."
+},
+"partitionEventRecord": {
+"$ref": "PartitionEventRecord",
+"description": "Partition event record describing key range changes for a change stream partition."
+},
+"partitionStartRecord": {
+"$ref": "PartitionStartRecord",
+"description": "Partition start record describing a new change stream partition."
+}
+},
+"type": "object"
+},
 "ChildLink": {
 "description": "Metadata associated with a parent-child relationship appearing in a PlanNode.",
 "id": "ChildLink",
@@ -3986,6 +4013,30 @@
 },
 "type": "object"
 },
+"ColumnMetadata": {
+"description": "Metadata for a column.",
+"id": "ColumnMetadata",
+"properties": {
+"isPrimaryKey": {
+"description": "Indicates whether the column is a primary key column.",
+"type": "boolean"
+},
+"name": {
+"description": "Name of the column.",
+"type": "string"
+},
+"ordinalPosition": {
+"description": "Ordinal position of the column based on the original table definition in the schema starting with a value of 1.",
+"format": "int64",
+"type": "string"
+},
+"type": {
+"$ref": "Type",
+"description": "Type of the column."
+}
+},
+"type": "object"
+},
 "CommitRequest": {
 "description": "The request for Commit.",
 "id": "CommitRequest",
@@ -4456,6 +4507,100 @@
 },
 "type": "object"
 },
+"DataChangeRecord": {
+"description": "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.",
+"id": "DataChangeRecord",
+"properties": {
+"columnMetadata": {
+"description": "Provides metadata describing the columns associated with the mods listed below.",
+"items": {
+"$ref": "ColumnMetadata"
+},
+"type": "array"
+},
+"commitTimestamp": {
+"description": "Indicates the timestamp in which the change was committed. DataChangeRecord.commit_timestamps, PartitionStartRecord.start_timestamps, PartitionEventRecord.commit_timestamps, and PartitionEndRecord.end_timestamps can have the same value in the same partition.",
+"format": "google-datetime",
+"type": "string"
+},
+"isLastRecordInTransactionInPartition": {
+"description": "Indicates whether this is the last record for a transaction in the current partition. Clients can use this field to determine when all records for a transaction in the current partition have been received.",
+"type": "boolean"
+},
+"isSystemTransaction": {
+"description": "Indicates whether the transaction is a system transaction. System transactions include those issued by time-to-live (TTL), column backfill, etc.",
+"type": "boolean"
+},
+"modType": {
+"description": "Describes the type of change.",
+"enum": [
+"MOD_TYPE_UNSPECIFIED",
+"INSERT",
+"UPDATE",
+"DELETE"
+],
+"enumDescriptions": [
+"Not specified.",
+"Indicates data was inserted.",
+"Indicates existing data was updated.",
+"Indicates existing data was deleted."
+],
+"type": "string"
+},
+"mods": {
+"description": "Describes the changes that were made.",
+"items": {
+"$ref": "Mod"
+},
+"type": "array"
+},
+"numberOfPartitionsInTransaction": {
+"description": "Indicates the number of partitions that return data change records for this transaction. This value can be helpful in assembling all records associated with a particular transaction.",
+"format": "int32",
+"type": "integer"
+},
+"numberOfRecordsInTransaction": {
+"description": "Indicates the number of data change records that are part of this transaction across all change stream partitions. This value can be used to assemble all the records associated with a particular transaction.",
+"format": "int32",
+"type": "integer"
+},
+"recordSequence": {
+"description": "Record sequence numbers are unique and monotonically increasing (but not necessarily contiguous) for a specific timestamp across record types in the same partition. To guarantee ordered processing, the reader should process records (of potentially different types) in record_sequence order for a specific timestamp in the same partition. The record sequence number ordering across partitions is only meaningful in the context of a specific transaction. Record sequence numbers are unique across partitions for a specific transaction. Sort the DataChangeRecords for the same server_transaction_id by record_sequence to reconstruct the ordering of the changes within the transaction.",
+"type": "string"
+},
+"serverTransactionId": {
+"description": "Provides a globally unique string that represents the transaction in which the change was committed. Multiple transactions can have the same commit timestamp, but each transaction has a unique server_transaction_id.",
+"type": "string"
+},
+"table": {
+"description": "Name of the table affected by the change.",
+"type": "string"
+},
+"transactionTag": {
+"description": "Indicates the transaction tag associated with this transaction.",
+"type": "string"
+},
+"valueCaptureType": {
+"description": "Describes the value capture type that was specified in the change stream configuration when this change was captured.",
+"enum": [
+"VALUE_CAPTURE_TYPE_UNSPECIFIED",
+"OLD_AND_NEW_VALUES",
+"NEW_VALUES",
+"NEW_ROW",
+"NEW_ROW_AND_OLD_VALUES"
+],
+"enumDescriptions": [
+"Not specified.",
+"Records both old and new values of the modified watched columns.",
+"Records only new values of the modified watched columns.",
+"Records new values of all watched columns, including modified and unmodified columns.",
+"Records the new values of all watched columns, including modified and unmodified columns. Also records the old values of the modified columns."
+],
+"type": "string"
+}
+},
+"type": "object"
+},
 "Database": {
 "description": "A Cloud Spanner database.",
 "id": "Database",
@@ -5018,6 +5163,18 @@
 },
 "type": "object"
 },
+"HeartbeatRecord": {
+"description": "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.",
+"id": "HeartbeatRecord",
+"properties": {
+"timestamp": {
+"description": "Indicates the timestamp at which the query has returned all the records in the change stream partition with timestamp <= heartbeat timestamp. The heartbeat timestamp will not be the same as the timestamps of other record types in the same partition.",
+"format": "google-datetime",
+"type": "string"
+}
+},
+"type": "object"
+},
 "IncludeReplicas": {
 "description": "An `IncludeReplicas` contains a repeated set of `ReplicaSelection` which indicates the order in which replicas should be considered.",
 "id": "IncludeReplicas",
@@ -6020,6 +6177,61 @@
 },
 "type": "object"
 },
+"Mod": {
+"description": "A mod describes all data changes in a watched table row.",
+"id": "Mod",
+"properties": {
+"keys": {
+"description": "Returns the value of the primary key of the modified row.",
+"items": {
+"$ref": "ModValue"
+},
+"type": "array"
+},
+"newValues": {
+"description": "Returns the new values after the change for the modified columns. Always empty for DELETE.",
+"items": {
+"$ref": "ModValue"
+},
+"type": "array"
+},
+"oldValues": {
+"description": "Returns the old values before the change for the modified columns. Always empty for INSERT, or if old values are not being captured specified by value_capture_type.",
+"items": {
+"$ref": "ModValue"
+},
+"type": "array"
+}
+},
+"type": "object"
+},
+"ModValue": {
+"description": "Returns the value and associated metadata for a particular field of the Mod.",
+"id": "ModValue",
+"properties": {
+"columnMetadataIndex": {
+"description": "Index within the repeated column_metadata field, to obtain the column metadata for the column that was modified.",
+"format": "int32",
+"type": "integer"
+},
+"value": {
+"description": "The value of the column.",
+"type": "any"
+}
+},
+"type": "object"
+},
+"MoveInEvent": {
+"description": "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.",
+"id": "MoveInEvent",
+"properties": {
+"sourcePartitionToken": {
+"description": "An unique partition identifier describing the source change stream partition that recorded changes for the key range that is moving into this partition.",
+"type": "string"
+}
+},
+"type": "object"
+},
 "MoveInstanceRequest": {
 "description": "The request for MoveInstance.",
 "id": "MoveInstanceRequest",
@@ -6038,6 +6250,17 @@
 },
 "type": "object"
 },
+"MoveOutEvent": {
+"description": "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.",
+"id": "MoveOutEvent",
+"properties": {
+"destinationPartitionToken": {
+"description": "An unique partition identifier describing the destination change stream partition that will record changes for the key range that is moving out of this partition.",
+"type": "string"
+}
+},
+"type": "object"
+},
 "MultiplexedSessionPrecommitToken": {
 "description": "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.",
 "id": "MultiplexedSessionPrecommitToken",
@@ -6219,6 +6442,60 @@
 },
 "type": "object"
 },
+"PartitionEndRecord": {
+"description": "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.",
+"id": "PartitionEndRecord",
+"properties": {
+"endTimestamp": {
+"description": "End timestamp at which the change stream partition is terminated. All changes generated by this partition will have timestamps <= end_timestamp. DataChangeRecord.commit_timestamps, PartitionStartRecord.start_timestamps, PartitionEventRecord.commit_timestamps, and PartitionEndRecord.end_timestamps can have the same value in the same partition. PartitionEndRecord is the last record returned for a partition.",
+"format": "google-datetime",
+"type": "string"
+},
+"partitionToken": {
+"description": "Unique partition identifier describing the terminated change stream partition. partition_token is equal to the partition token of the change stream partition currently queried to return this PartitionEndRecord.",
+"type": "string"
+},
+"recordSequence": {
+"description": "Record sequence numbers are unique and monotonically increasing (but not necessarily contiguous) for a specific timestamp across record types in the same partition. To guarantee ordered processing, the reader should process records (of potentially different types) in record_sequence order for a specific timestamp in the same partition.",
+"type": "string"
+}
+},
+"type": "object"
+},
+"PartitionEventRecord": {
+"description": "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.",
+"id": "PartitionEventRecord",
+"properties": {
+"commitTimestamp": {
+"description": "Indicates the commit timestamp at which the key range change occurred. DataChangeRecord.commit_timestamps, PartitionStartRecord.start_timestamps, PartitionEventRecord.commit_timestamps, and PartitionEndRecord.end_timestamps can have the same value in the same partition.",
+"format": "google-datetime",
+"type": "string"
+},
+"moveInEvents": {
+"description": "Set when one or more key ranges are moved into the change stream partition identified by partition_token. Example: Two key ranges are moved into partition (P1) from partition (P2) and partition (P3) in a single transaction at timestamp T. The PartitionEventRecord returned in P1 will reflect the move as: PartitionEventRecord { commit_timestamp: T partition_token: \"P1\" move_in_events { source_partition_token: \"P2\" } move_in_events { source_partition_token: \"P3\" } } The PartitionEventRecord returned in P2 will reflect the move as: PartitionEventRecord { commit_timestamp: T partition_token: \"P2\" move_out_events { destination_partition_token: \"P1\" } } The PartitionEventRecord returned in P3 will reflect the move as: PartitionEventRecord { commit_timestamp: T partition_token: \"P3\" move_out_events { destination_partition_token: \"P1\" } }",
+"items": {
+"$ref": "MoveInEvent"
+},
+"type": "array"
+},
+"moveOutEvents": {
+"description": "Set when one or more key ranges are moved out of the change stream partition identified by partition_token. Example: Two key ranges are moved out of partition (P1) to partition (P2) and partition (P3) in a single transaction at timestamp T. The PartitionEventRecord returned in P1 will reflect the move as: PartitionEventRecord { commit_timestamp: T partition_token: \"P1\" move_out_events { destination_partition_token: \"P2\" } move_out_events { destination_partition_token: \"P3\" } } The PartitionEventRecord returned in P2 will reflect the move as: PartitionEventRecord { commit_timestamp: T partition_token: \"P2\" move_in_events { source_partition_token: \"P1\" } } The PartitionEventRecord returned in P3 will reflect the move as: PartitionEventRecord { commit_timestamp: T partition_token: \"P3\" move_in_events { source_partition_token: \"P1\" } }",
+"items": {
+"$ref": "MoveOutEvent"
+},
+"type": "array"
+},
+"partitionToken": {
+"description": "Unique partition identifier describing the partition this event occurred on. partition_token is equal to the partition token of the change stream partition currently queried to return this PartitionEventRecord.",
+"type": "string"
+},
+"recordSequence": {
+"description": "Record sequence numbers are unique and monotonically increasing (but not necessarily contiguous) for a specific timestamp across record types in the same partition. To guarantee ordered processing, the reader should process records (of potentially different types) in record_sequence order for a specific timestamp in the same partition.",
+"type": "string"
+}
+},
+"type": "object"
+},
 "PartitionOptions": {
 "description": "Options for a `PartitionQueryRequest` and `PartitionReadRequest`.",
 "id": "PartitionOptions",
@@ -6322,6 +6599,29 @@
 },
 "type": "object"
 },
+"PartitionStartRecord": {
+"description": "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.",
+"id": "PartitionStartRecord",
+"properties": {
+"partitionTokens": {
+"description": "Unique partition identifiers to be used in queries.",
+"items": {
+"type": "string"
+},
+"type": "array"
+},
+"recordSequence": {
+"description": "Record sequence numbers are unique and monotonically increasing (but not necessarily contiguous) for a specific timestamp across record types in the same partition. To guarantee ordered processing, the reader should process records (of potentially different types) in record_sequence order for a specific timestamp in the same partition.",
+"type": "string"
+},
+"startTimestamp": {
+"description": "Start timestamp at which the partitions should be queried to return change stream records with timestamps >= start_timestamp. DataChangeRecord.commit_timestamps, PartitionStartRecord.start_timestamps, PartitionEventRecord.commit_timestamps, and PartitionEndRecord.end_timestamps can have the same value in the same partition.",
+"format": "google-datetime",
+"type": "string"
+}
+},
+"type": "object"
+},
 "PartitionedDml": {
 "description": "Message type to initiate a Partitioned DML transaction.",
 "id": "PartitionedDml",
@@ -7276,7 +7576,7 @@
 "type": "object"
 },
 "TransactionOptions": {
-"description": "Transactions: Each session can have at most one active transaction at a time (note that standalone reads and queries use a transaction internally and do count towards the one transaction limit). After the active transaction is completed, the session can immediately be re-used for the next transaction. It is not necessary to create a new session for each transaction. Transaction modes: Cloud Spanner supports three transaction modes: 1. Locking read-write. This type of transaction is the only way to write data into Cloud Spanner. These transactions rely on pessimistic locking and, if necessary, two-phase commit. Locking read-write transactions may abort, requiring the application to retry. 2. Snapshot read-only. Snapshot read-only transactions provide guaranteed consistency across several reads, but do not allow writes. Snapshot read-only transactions can be configured to read at timestamps in the past, or configured to perform a strong read (where Spanner selects a timestamp such that the read is guaranteed to see the effects of all transactions that have committed before the start of the read). Snapshot read-only transactions do not need to be committed. Queries on change streams must be performed with the snapshot read-only transaction mode, specifying a strong read. See TransactionOptions.ReadOnly.strong for more details. 3. Partitioned DML. This type of transaction is used to execute a single Partitioned DML statement. Partitioned DML partitions the key space and runs the DML statement over each partition in parallel using separate, internal transactions that commit independently. Partitioned DML transactions do not need to be committed. For transactions that only read, snapshot read-only transactions provide simpler semantics and are almost always faster. In particular, read-only transactions do not take locks, so they do not conflict with read-write transactions. As a consequence of not taking locks, they also do not abort, so retry loops are not needed. Transactions may only read-write data in a single database. They may, however, read-write data in different tables within that database. Locking read-write transactions: Locking transactions may be used to atomically read-modify-write data anywhere in a database. This type of transaction is externally consistent. Clients should attempt to minimize the amount of time a transaction is active. Faster transactions commit with higher probability and cause less contention. Cloud Spanner attempts to keep read locks active as long as the transaction continues to do reads, and the transaction has not been terminated by Commit or Rollback. Long periods of inactivity at the client may cause Cloud Spanner to release a transaction's locks and abort it. Conceptually, a read-write transaction consists of zero or more reads or SQL statements followed by Commit. At any time before Commit, the client can send a Rollback request to abort the transaction. Semantics: Cloud Spanner can commit the transaction if all read locks it acquired are still valid at commit time, and it is able to acquire write locks for all writes. Cloud Spanner can abort the transaction for any reason. If a commit attempt returns `ABORTED`, Cloud Spanner guarantees that the transaction has not modified any user data in Cloud Spanner. Unless the transaction commits, Cloud Spanner makes no guarantees about how long the transaction's locks were held for. It is an error to use Cloud Spanner locks for any sort of mutual exclusion other than between Cloud Spanner transactions themselves. Retrying aborted transactions: When a transaction aborts, the application can choose to retry the whole transaction again. To maximize the chances of successfully committing the retry, the client should execute the retry in the same session as the original attempt. The original session's lock priority increases with each consecutive abort, meaning that each attempt has a slightly better chance of success than the previous. Note that the lock priority is preserved per session (not per transaction). Lock priority is set by the first read or write in the first attempt of a read-write transaction. If the application starts a new session to retry the whole transaction, the transaction loses its original lock priority. Moreover, the lock priority is only preserved if the transaction fails with an `ABORTED` error. Under some circumstances (for example, many transactions attempting to modify the same row(s)), a transaction can abort many times in a short period before successfully committing. Thus, it is not a good idea to cap the number of retries a transaction can attempt; instead, it is better to limit the total amount of time spent retrying. Idle transactions: A transaction is considered idle if it has no outstanding reads or SQL queries and has not started a read or SQL query within the last 10 seconds. Idle transactions can be aborted by Cloud Spanner so that they don't hold on to locks indefinitely. If an idle transaction is aborted, the commit fails with error `ABORTED`. If this behavior is undesirable, periodically executing a simple SQL query in the transaction (for example, `SELECT 1`) prevents the transaction from becoming idle. Snapshot read-only transactions: Snapshot read-only transactions provides a simpler method than locking read-write transactions for doing several consistent reads. However, this type of transaction does not support writes. Snapshot transactions do not take locks. Instead, they work by choosing a Cloud Spanner timestamp, then executing all reads at that timestamp. Since they do not acquire locks, they do not block concurrent read-write transactions. Unlike locking read-write transactions, snapshot read-only transactions never abort. They can fail if the chosen read timestamp is garbage collected; however, the default garbage collection policy is generous enough that most applications do not need to worry about this in practice. Snapshot read-only transactions do not need to call Commit or Rollback (and in fact are not permitted to do so). To execute a snapshot transaction, the client specifies a timestamp bound, which tells Cloud Spanner how to choose a read timestamp. The types of timestamp bound are: - Strong (the default). - Bounded staleness. - Exact staleness. If the Cloud Spanner database to be read is geographically distributed, stale read-only transactions can execute more quickly than strong or read-write transactions, because they are able to execute far from the leader replica. Each type of timestamp bound is discussed in detail below. Strong: Strong reads are guaranteed to see the effects of all transactions that have committed before the start of the read. Furthermore, all rows yielded by a single read are consistent with each other -- if any part of the read observes a transaction, all parts of the read see the transaction. Strong reads are not repeatable: two consecutive strong read-only transactions might return inconsistent results if there are concurrent writes. If consistency across reads is required, the reads should be executed within a transaction or at an exact read timestamp. Queries on change streams (see below for more details) must also specify the strong read timestamp bound. See TransactionOptions.ReadOnly.strong. Exact staleness: These timestamp bounds execute reads at a user-specified timestamp. Reads at a timestamp are guaranteed to see a consistent prefix of the global transaction history: they observe modifications done by all transactions with a commit timestamp less than or equal to the read timestamp, and observe none of the modifications done by transactions with a larger commit timestamp. They block until all conflicting transactions that can be assigned commit timestamps <= the read timestamp have finished. The timestamp can either be expressed as an absolute Cloud Spanner commit timestamp or a staleness relative to the current time. These modes do not require a \"negotiation phase\" to pick a timestamp. As a result, they execute slightly faster than the equivalent boundedly stale concurrency modes. On the other hand, boundedly stale reads usually return fresher results. See TransactionOptions.ReadOnly.read_timestamp and TransactionOptions.ReadOnly.exact_staleness. Bounded staleness: Bounded staleness modes allow Cloud Spanner to pick the read timestamp, subject to a user-provided staleness bound. Cloud Spanner chooses the newest timestamp within the staleness bound that allows execution of the reads at the closest available replica without blocking. All rows yielded are consistent with each other -- if any part of the read observes a transaction, all parts of the read see the transaction. Boundedly stale reads are not repeatable: two stale reads, even if they use the same staleness bound, can execute at different timestamps and thus return inconsistent results. Boundedly stale reads execute in two phases: the first phase negotiates a timestamp among all replicas needed to serve the read. In the second phase, reads are executed at the negotiated timestamp. As a result of the two phase execution, bounded staleness reads are usually a little slower than comparable exact staleness reads. However, they are typically able to return fresher results, and are more likely to execute at the closest replica. Because the timestamp negotiation requires up-front knowledge of which rows are read, it can only be used with single-use read-only transactions. See TransactionOptions.ReadOnly.max_staleness and TransactionOptions.ReadOnly.min_read_timestamp. Old read timestamps and garbage collection: Cloud Spanner continuously garbage collects deleted and overwritten data in the background to reclaim storage space. This process is known as \"version GC\". By default, version GC reclaims versions after they are one hour old. Because of this, Cloud Spanner can't perform reads at read timestamps more than one hour in the past. This restriction also applies to in-progress reads and/or SQL queries whose timestamp become too old while executing. Reads and SQL queries with too-old read timestamps fail with the error `FAILED_PRECONDITION`. You can configure and extend the `VERSION_RETENTION_PERIOD` of a database up to a period as long as one week, which allows Cloud Spanner to perform reads up to one week in the past. Querying change Streams: A Change Stream is a schema object that can be configured to watch data changes on the entire database, a set of tables, or a set of columns in a database. When a change stream is created, Spanner automatically defines a corresponding SQL Table-Valued Function (TVF) that can be used to query the change records in the associated change stream using the ExecuteStreamingSql API. The name of the TVF for a change stream is generated from the name of the change stream: READ_. All queries on change stream TVFs must be executed using the ExecuteStreamingSql API with a single-use read-only transaction with a strong read-only timestamp_bound. The change stream TVF allows users to specify the start_timestamp and end_timestamp for the time range of interest. All change records within the retention period is accessible using the strong read-only timestamp_bound. All other TransactionOptions are invalid for change stream queries. In addition, if TransactionOptions.read_only.return_read_timestamp is set to true, a special value of 2^63 - 2 is returned in the Transaction message that describes the transaction, instead of a valid read timestamp. This special value should be discarded and not used for any subsequent queries. Please see https://cloud.google.com/spanner/docs/change-streams for more details on how to query the change stream TVFs. Partitioned DML transactions: Partitioned DML transactions are used to execute DML statements with a different execution strategy that provides different, and often better, scalability properties for large, table-wide operations than DML in a ReadWrite transaction. Smaller scoped statements, such as an OLTP workload, should prefer using ReadWrite transactions. Partitioned DML partitions the keyspace and runs the DML statement on each partition in separate, internal transactions. These transactions commit automatically when complete, and run independently from one another. To reduce lock contention, this execution strategy only acquires read locks on rows that match the WHERE clause of the statement. Additionally, the smaller per-partition transactions hold locks for less time. That said, Partitioned DML is not a drop-in replacement for standard DML used in ReadWrite transactions. - The DML statement must be fully-partitionable. Specifically, the statement must be expressible as the union of many statements which each access only a single row of the table. - The statement is not applied atomically to all rows of the table. Rather, the statement is applied atomically to partitions of the table, in independent transactions. Secondary index rows are updated atomically with the base table rows. - Partitioned DML does not guarantee exactly-once execution semantics against a partition. The statement is applied at least once to each partition. It is strongly recommended that the DML statement should be idempotent to avoid unexpected results. For instance, it is potentially dangerous to run a statement such as `UPDATE table SET column = column + 1` as it could be run multiple times against some rows. - The partitions are committed automatically - there is no support for Commit or Rollback. If the call returns an error, or if the client issuing the ExecuteSql call dies, it is possible that some rows had the statement executed on them successfully. It is also possible that statement was never executed against other rows. - Partitioned DML transactions may only contain the execution of a single DML statement via ExecuteSql or ExecuteStreamingSql. - If any error is encountered during the execution of the partitioned DML operation (for instance, a UNIQUE INDEX violation, division by zero, or a value that can't be stored due to schema constraints), then the operation is stopped at that point and an error is returned. It is possible that at this point, some partitions have been committed (or even committed multiple times), and other partitions have not been run at all. Given the above, Partitioned DML is good fit for large, database-wide, operations that are idempotent, such as deleting old rows from a very large table.",
+"description": "Options to use for transactions.",
 "id": "TransactionOptions",
 "properties": {
 "excludeTxnFromChangeStreams": {

googleapiclient/discovery_cache/documents/storage.v1.json

@@ -253,7 +253,7 @@
 "location": "northamerica-south1"
 }
 ],
-"etag": "\"36383730363437323837383838393538333732\"",
+"etag": "\"31353834363234393531343533373938353433\"",
 "icons": {
 "x16": "https://www.google.com/images/icons/product/cloud_storage-16.png",
 "x32": "https://www.google.com/images/icons/product/cloud_storage-32.png"
@@ -3306,6 +3306,11 @@
 "location": "query",
 "type": "string"
 },
+"filter": {
+"description": "Filter the returned objects. Currently only supported for the contexts field. If delimiter is set, the returned prefixes are exempt from this filter.",
+"location": "query",
+"type": "string"
+},
 "includeFoldersAsPrefixes": {
 "description": "Only applicable if delimiter is set to '/'. If true, will also include folders and managed folders (besides objects) in the returned prefixes.",
 "location": "query",
@@ -4539,7 +4544,7 @@
 }
 }
 },
-"revision": "20250605",
+"revision": "20250629",
 "rootUrl": "https://storage.googleapis.com/",
 "schemas": {
 "AdvanceRelocateBucketOperationRequest": {
@@ -5932,6 +5937,20 @@
 "description": "Content-Type of the object data. If an object is stored without a Content-Type, it is served as application/octet-stream.",
 "type": "string"
 },
+"contexts": {
+"description": "User-defined or system-defined object contexts. Each object context is a key-payload pair, where the key provides the identification and the payload holds the associated value and additional metadata.",
+"properties": {
+"custom": {
+"additionalProperties": {
+"$ref": "ObjectCustomContextPayload",
+"description": "A single user-defined object context."
+},
+"description": "User-defined object contexts.",
+"type": "object"
+}
+},
+"type": "object"
+},
 "crc32c": {
 "description": "CRC32c checksum, as described in RFC 4960, Appendix B; encoded using base64 in big-endian byte order. For more information about using the CRC32c checksum, see [Data Validation and Change Detection](https://cloud.google.com/storage/docs/data-validation).",
 "type": "string"
@@ -6201,6 +6220,27 @@
 },
 "type": "object"
 },
+"ObjectCustomContextPayload": {
+"description": "The payload of a single user-defined object context.",
+"id": "ObjectCustomContextPayload",
+"properties": {
+"createTime": {
+"description": "The time at which the object context was created in RFC 3339 format.",
+"format": "date-time",
+"type": "string"
+},
+"updateTime": {
+"description": "The time at which the object context was last updated in RFC 3339 format.",
+"format": "date-time",
+"type": "string"
+},
+"value": {
+"description": "The value of the object context.",
+"type": "string"
+}
+},
+"type": "object"
+},
 "Objects": {
 "description": "A list of objects.",
 "id": "Objects",

googleapiclient/discovery_cache/documents/testing.v1.json

@@ -454,7 +454,7 @@
 }
 }
 },
-"revision": "20250327",
+"revision": "20250624",
 "rootUrl": "https://testing.googleapis.com/",
 "schemas": {
 "Account": {
@@ -1016,10 +1016,28 @@
 },
 "type": "object"
 },
+"ApkSplits": {
+"description": "A single dynamic feature apk.",
+"id": "ApkSplits",
+"properties": {
+"bundleSplits": {
+"description": "A list of .apk files generated by bundletool to install to the device under test as a single android app with adb install-multiple. If specified, requires one or more bundle_splits. The first split specified represents the base APK, while subsequent splits represent feature apks.",
+"items": {
+"$ref": "FileReference"
+},
+"type": "array"
+}
+},
+"type": "object"
+},
 "AppBundle": {
 "description": "An Android App Bundle file format, containing a BundleConfig.pb file, a base module directory, zero or more dynamic feature module directories. See https://developer.android.com/guide/app-bundle/build for guidance on building App Bundles.",
 "id": "AppBundle",
 "properties": {
+"apks": {
+"$ref": "ApkSplits",
+"description": ".apk files generated by bundletool to install as a single android app."
+},
 "bundleLocation": {
 "$ref": "FileReference",
 "description": ".aab file representing the app bundle under test."

googleapiclient/discovery_cache/documents/trafficdirector.v3.json

@@ -128,7 +128,7 @@
 }
 }
 },
-"revision": "20250516",
+"revision": "20250618",
 "rootUrl": "https://trafficdirector.googleapis.com/",
 "schemas": {
 "Address": {
@@ -1118,7 +1118,7 @@
 "type": "string"
 },
 "networkNamespaceFilepath": {
-"description": "The Linux network namespace to bind the socket to. If this is set, Envoy will create the socket in the specified network namespace. Only supported on Linux. [#not-implemented-hide:]",
+"description": "Filepath that specifies the Linux network namespace this socket will be created in (see ``man 7 network_namespaces``). If this field is set, Envoy will create the socket in the specified network namespace. .. note:: Setting this parameter requires Envoy to run with the ``CAP_NET_ADMIN`` capability. .. note:: Currently only used for Listener sockets. .. attention:: Network namespaces are only configurable on Linux. Otherwise, this field has no effect.",
 "type": "string"
 },
 "portValue": {

googleapiclient/discovery_cache/documents/travelimpactmodel.v1.json

@@ -131,7 +131,7 @@
 }
 }
 },
-"revision": "20250605",
+"revision": "20250624",
 "rootUrl": "https://travelimpactmodel.googleapis.com/",
 "schemas": {
 "ComputeFlightEmissionsRequest": {
@@ -220,6 +220,30 @@
 },
 "type": "object"
 },
+"EasaLabelMetadata": {
+"description": "Metadata about the EASA Flight Emissions Label.",
+"id": "EasaLabelMetadata",
+"properties": {
+"labelExpiryDate": {
+"$ref": "Date",
+"description": "The date when the label expires. The label can be displayed until the end of this date."
+},
+"labelIssueDate": {
+"$ref": "Date",
+"description": "The date when the label was issued."
+},
+"labelVersion": {
+"description": "Version of the label.",
+"type": "string"
+},
+"safDiscountPercentage": {
+"description": "Sustainable Aviation Fuel (SAF) emissions discount percentage applied to the label. It is a percentage as a decimal. The values are in the interval [0,1]. For example, 0.0021 means 0.21%. This discount and reduction in emissions are reported by the EASA label but they are not included in the CO2e estimates distributed by this API.",
+"format": "double",
+"type": "number"
+}
+},
+"type": "object"
+},
 "EmissionsGramsPerPax": {
 "description": "Grouped emissions per seating class results.",
 "id": "EmissionsGramsPerPax",
@@ -279,6 +303,26 @@
 "description": "Direct flight with emission estimates.",
 "id": "FlightWithEmissions",
 "properties": {
+"contrailsImpactBucket": {
+"description": "Optional. The significance of contrails warming impact compared to the total CO2e emissions impact.",
+"enum": [
+"CONTRAILS_IMPACT_UNSPECIFIED",
+"CONTRAILS_IMPACT_NEGLIGIBLE",
+"CONTRAILS_IMPACT_MODERATE",
+"CONTRAILS_IMPACT_SEVERE"
+],
+"enumDescriptions": [
+"The contrails impact is unspecified.",
+"The contrails impact is negligible compared to the total CO2e emissions.",
+"The contrails impact is comparable to the total CO2e emissions.",
+"The contrails impact is higher than the total CO2e emissions impact."
+],
+"type": "string"
+},
+"easaLabelMetadata": {
+"$ref": "EasaLabelMetadata",
+"description": "Optional. Metadata about the EASA Flight Emissions Label. Only set when the emissions data source is EASA."
+},
 "emissionsGramsPerPax": {
 "$ref": "EmissionsGramsPerPax",
 "description": "Optional. Per-passenger emission estimate numbers. Will not be present if emissions could not be computed. For the list of reasons why emissions could not be computed, see ComputeFlightEmissions."
@@ -286,6 +330,20 @@
 "flight": {
 "$ref": "Flight",
 "description": "Required. Matches the flight identifiers in the request. Note: all IATA codes are capitalized."
+},
+"source": {
+"description": "Optional. The source of the emissions data.",
+"enum": [
+"SOURCE_UNSPECIFIED",
+"TIM",
+"EASA"
+],
+"enumDescriptions": [
+"The source of the emissions data is unspecified.",
+"The emissions data is from the Travel Impact Model.",
+"The emissions data is from the EASA environmental labels."
+],
+"type": "string"
 }
 },
 "type": "object"

googleapiclient/discovery_cache/documents/vault.v1.json

@@ -1203,7 +1203,7 @@
 }
 }
 },
-"revision": "20250527",
+"revision": "20250616",
 "rootUrl": "https://vault.googleapis.com/",
 "schemas": {
 "AccountCount": {
@@ -1654,7 +1654,7 @@
 "enumDescriptions": [
 "No shared drive option specified.",
 "If a resource is in a shared drive, it isn't included in the search.",
-"(Previously \"include_shared_drives\" off)",
+"Shared drive resources are only included in instances where the account is a collaborator on a resource but they are not a member of the shared drive. This maps to the *\"Included only if documents shared directly (not due to shared drive membership)\"* option in the Vault UI. (Previously \"include_shared_drives\" off)",
 "Resources in shared drives are included in the search. (Previously \"include_shared_drives\" on)"
 ],
 "type": "string"