View Source API Reference google_api_datastore v0.22.0
Modules
API client metadata for GoogleApi.Datastore.V1.
API calls for all endpoints tagged Projects.
Handle Tesla connections for GoogleApi.Datastore.V1.
Defines an aggregation that produces a single result.
Datastore query for running an aggregation over a Query.
The result of a single bucket from a Datastore aggregation query. The keys of aggregate_properties are the same for all results in an aggregation query, unlike entity queries which can have different fields present for each result.
A batch of aggregation results produced by an aggregation query.
The request for Datastore.AllocateIds.
The response for Datastore.AllocateIds.
An array value.
Average of the values of the requested property. Only numeric values will be aggregated. All non-numeric values including NULL are skipped. If the aggregated values contain NaN, returns NaN. Infinity math follows IEEE-754 standards. If the aggregated value set is empty, returns NULL. Always returns the result as a double.
The request for Datastore.BeginTransaction.
The response for Datastore.BeginTransaction.
The request for Datastore.Commit.
The response for Datastore.Commit.
A filter that merges multiple other filters using the given operator.
Count of entities that match the query. The COUNT(*) aggregation function operates on the entire entity so it does not require a field reference.
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); }
A Datastore data object. Must not exceed 1 MiB - 4 bytes.
The result of fetching an entity from Datastore.
Execution statistics for the query.
Explain metrics for the query.
Explain options for the query.
A holder for any type of filter.
Metadata common to all Datastore Admin operations.
Metadata for Datastore to Firestore migration operations. The DatastoreFirestoreMigration operation is not started by the end-user via an explicit "creation" method. This is an intentional deviation from the LRO design pattern. This singleton resource can be accessed at: "projects/{project_id}/operations/datastore-firestore-migration"
Identifies a subset of entities in a project. This is specified as combinations of kinds and namespaces (either or both of which may be all, as described in the following examples). Example usage: Entire project: kinds=[], namespace_ids=[] Kinds Foo and Bar in all namespaces: kinds=['Foo', 'Bar'], namespace_ids=[] Kinds Foo and Bar only in the default namespace: kinds=['Foo', 'Bar'], namespace_ids=[''] Kinds Foo and Bar in both the default and Baz namespaces: kinds=['Foo', 'Bar'], namespace_ids=['', 'Baz'] The entire Baz namespace: kinds=[], namespace_ids=['Baz']
Metadata for ExportEntities operations.
The request for google.datastore.admin.v1.DatastoreAdmin.ExportEntities.
The response for google.datastore.admin.v1.DatastoreAdmin.ExportEntities.
Metadata for ImportEntities operations.
The request for google.datastore.admin.v1.DatastoreAdmin.ImportEntities.
Datastore composite index definition.
Metadata for Index operations.
A property of an index.
The response for google.datastore.admin.v1.DatastoreAdmin.ListIndexes.
An event signifying the start of a new step in a migration from Cloud Datastore to Cloud Firestore in Datastore mode.
An event signifying a change in state of a migration from Cloud Datastore to Cloud Firestore in Datastore mode.
Details for the PREPARE step.
Measures the progress of a particular metric.
Details for the REDIRECT_WRITES step.
Metadata common to all Datastore Admin operations.
Identifies a subset of entities in a project. This is specified as combinations of kinds and namespaces (either or both of which may be all, as described in the following examples). Example usage: Entire project: kinds=[], namespace_ids=[] Kinds Foo and Bar in all namespaces: kinds=['Foo', 'Bar'], namespace_ids=[] Kinds Foo and Bar only in the default namespace: kinds=['Foo', 'Bar'], namespace_ids=[''] Kinds Foo and Bar in both the default and Baz namespaces: kinds=['Foo', 'Bar'], namespace_ids=['', 'Baz'] The entire Baz namespace: kinds=[], namespace_ids=['Baz']
Metadata for ExportEntities operations.
The response for google.datastore.admin.v1beta1.DatastoreAdmin.ExportEntities.
Metadata for ImportEntities operations.
Measures the progress of a particular metric.
The response message for Operations.ListOperations.
This resource represents a long-running operation that is the result of a network API call.
A binding parameter for a GQL query.
A unique identifier for an entity. If a key's partition ID or any of its path kinds or names are reserved/read-only, the key is reserved/read-only. A reserved/read-only key is forbidden in certain documented contexts.
A representation of a kind.
An object that represents a latitude/longitude pair. This is expressed as a pair of doubles to represent degrees latitude and degrees longitude. Unless specified otherwise, this object must conform to the WGS84 standard. Values must be within normalized ranges.
The request for Datastore.Lookup.
The response for Datastore.Lookup.
A mutation to apply to an entity.
The result of applying a mutation.
A partition ID identifies a grouping of entities. The grouping is always by project and namespace, however the namespace ID may be empty. A partition ID contains several dimensions: project ID and namespace ID. Partition dimensions: - May be "". - Must be valid UTF-8 bytes. - Must have values that match regex [A-Za-z\d\.\-_]{1,100} If the value of any dimension matches regex __.*__, the partition is reserved/read-only. A reserved/read-only partition ID is forbidden in certain documented contexts. Foreign partition IDs (in which the project ID does not match the context project ID ) are discouraged. Reads and writes of foreign partition IDs may fail if the project is not in an active state.
A (kind, ID/name) pair used to construct a key path. If either name or ID is set, the element is complete. If neither is set, the element is incomplete.
Planning phase information for the query.
A representation of a property in a projection.
A filter on a specific property.
The set of arbitrarily nested property paths used to restrict an operation to only a subset of properties in an entity.
The desired order for a specific property.
A reference to a property relative to the kind expressions.
A query for entities.
A batch of results produced by a query.
Options specific to read-only transactions.
The options shared by read requests.
Options specific to read / write transactions.
The request for Datastore.ReserveIds.
The response for Datastore.ReserveIds.
The request for Datastore.Rollback.
The response for Datastore.Rollback. (an empty message).
The request for Datastore.RunAggregationQuery.
The response for Datastore.RunAggregationQuery.
The request for Datastore.RunQuery.
The response for Datastore.RunQuery.
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.
Sum of the values of the requested property. Only numeric values will be aggregated. All non-numeric values including NULL are skipped. If the aggregated values contain NaN, returns NaN. Infinity math follows IEEE-754 standards. If the aggregated value set is empty, returns 0. Returns a 64-bit integer if all aggregated numbers are integers and the sum result does not overflow. Otherwise, the result is returned as a double. Note that even if all the aggregated values are integers, the result is returned as a double if it cannot fit within a 64-bit signed integer. When this occurs, the returned value will lose precision. * When underflow occurs, floating-point aggregation is non-deterministic. This means that running the same query repeatedly without any changes to the underlying values could produce slightly different results each time. In those cases, values should be stored as integers over floating-point numbers.
Options for beginning a new transaction. Transactions can be created explicitly with calls to Datastore.BeginTransaction or implicitly by setting ReadOptions.new_transaction in read requests.
A message that can hold any of the supported value types and associated metadata.