Crate google_spanner1

source ·
Expand description

This documentation was generated from Spanner crate version 1.0.7+20180920, where 20180920 is the exact revision of the spanner:v1 schema built by the mako code generator v1.0.7.

Everything else about the Spanner v1 API can be found at the official documentation site. The original source code is on github.

§Features

Handle the following Resources with ease from the central hub

Not what you are looking for ? Find all other Google APIs in their Rust documentation index.

§Structure of this Library

The API is structured into the following primary items:

  • Hub
    • a central object to maintain state and allow accessing all Activities
    • creates Method Builders which in turn allow access to individual Call Builders
  • Resources
    • primary types that you can apply Activities to
    • a collection of properties and Parts
    • Parts
      • a collection of properties
      • never directly used in Activities
  • Activities
    • operations to apply to Resources

All structures are marked with applicable traits to further categorize them and ease browsing.

Generally speaking, you can invoke Activities like this:

let r = hub.resource().activity(...).doit()

Or specifically …

let r = hub.projects().instances_databases_operations_cancel(...).doit()
let r = hub.projects().instances_databases_drop_database(...).doit()
let r = hub.projects().instances_operations_delete(...).doit()
let r = hub.projects().instances_databases_operations_delete(...).doit()
let r = hub.projects().instances_delete(...).doit()
let r = hub.projects().instances_operations_cancel(...).doit()
let r = hub.projects().instances_databases_sessions_rollback(...).doit()
let r = hub.projects().instances_databases_sessions_delete(...).doit()

The resource() and activity(...) calls create builders. The second one dealing with Activities supports various methods to configure the impending operation (not shown here). It is made such that all required arguments have to be specified right away (i.e. (...)), whereas all optional ones can be build up as desired. The doit() method performs the actual communication with the server and returns the respective result.

§Usage

§Setting up your Project

To use this library, you would put the following lines into your Cargo.toml file:

[dependencies]
google-spanner1 = "*"
# This project intentionally uses an old version of Hyper. See
# https://github.com/Byron/google-apis-rs/issues/173 for more
# information.
hyper = "^0.10"
hyper-rustls = "^0.6"
serde = "^1.0"
serde_json = "^1.0"
yup-oauth2 = "^1.0"

§A complete example

extern crate hyper;
extern crate hyper_rustls;
extern crate yup_oauth2 as oauth2;
extern crate google_spanner1 as spanner1;
use spanner1::RollbackRequest;
use spanner1::{Result, Error};
use std::default::Default;
use oauth2::{Authenticator, DefaultAuthenticatorDelegate, ApplicationSecret, MemoryStorage};
use spanner1::Spanner;
 
// Get an ApplicationSecret instance by some means. It contains the `client_id` and 
// `client_secret`, among other things.
let secret: ApplicationSecret = Default::default();
// Instantiate the authenticator. It will choose a suitable authentication flow for you, 
// unless you replace  `None` with the desired Flow.
// Provide your own `AuthenticatorDelegate` to adjust the way it operates and get feedback about 
// what's going on. You probably want to bring in your own `TokenStorage` to persist tokens and
// retrieve them from storage.
let auth = Authenticator::new(&secret, DefaultAuthenticatorDelegate,
                              hyper::Client::with_connector(hyper::net::HttpsConnector::new(hyper_rustls::TlsClient::new())),
                              <MemoryStorage as Default>::default(), None);
let mut hub = Spanner::new(hyper::Client::with_connector(hyper::net::HttpsConnector::new(hyper_rustls::TlsClient::new())), auth);
// As the method needs a request, you would usually fill it with the desired information
// into the respective structure. Some of the parts shown here might not be applicable !
// Values shown here are possibly random and not representative !
let mut req = RollbackRequest::default();
 
// You can configure optional parameters by calling the respective setters at will, and
// execute the final call using `doit()`.
// Values shown here are possibly random and not representative !
let result = hub.projects().instances_databases_sessions_rollback(req, "session")
             .doit();
 
match result {
    Err(e) => match e {
        // The Error enum provides details about what exactly happened.
        // You can also just use its `Debug`, `Display` or `Error` traits
         Error::HttpError(_)
        |Error::MissingAPIKey
        |Error::MissingToken(_)
        |Error::Cancelled
        |Error::UploadSizeLimitExceeded(_, _)
        |Error::Failure(_)
        |Error::BadRequest(_)
        |Error::FieldClash(_)
        |Error::JsonDecodeError(_, _) => println!("{}", e),
    },
    Ok(res) => println!("Success: {:?}", res),
}

§Handling Errors

All errors produced by the system are provided either as Result enumeration as return value of the doit() methods, or handed as possibly intermediate results to either the Hub Delegate, or the Authenticator Delegate.

When delegates handle errors or intermediate values, they may have a chance to instruct the system to retry. This makes the system potentially resilient to all kinds of errors.

§Uploads and Downloads

If a method supports downloads, the response body, which is part of the Result, should be read by you to obtain the media. If such a method also supports a Response Result, it will return that by default. You can see it as meta-data for the actual media. To trigger a media download, you will have to set up the builder by making this call: .param("alt", "media").

Methods supporting uploads can do so using up to 2 different protocols: simple and resumable. The distinctiveness of each is represented by customized doit(...) methods, which are then named upload(...) and upload_resumable(...) respectively.

§Customization and Callbacks

You may alter the way an doit() method is called by providing a delegate to the Method Builder before making the final doit() call. Respective methods will be called to provide progress information, as well as determine whether the system should retry on failure.

The delegate trait is default-implemented, allowing you to customize it with minimal effort.

§Optional Parts in Server-Requests

All structures provided by this library are made to be enocodable and decodable via json. Optionals are used to indicate that partial requests are responses are valid. Most optionals are are considered Parts which are identifiable by name, which will be sent to the server to indicate either the set parts of the request or the desired parts in the response.

§Builder Arguments

Using method builders, you are able to prepare an action call by repeatedly calling it’s methods. These will always take a single argument, for which the following statements are true.

Arguments will always be copied or cloned into the builder, to make them independent of their original life times.

Structs§

  • The request for BeginTransaction.
  • Associates members with a role.
  • Metadata associated with a parent-child relationship appearing in a PlanNode.
  • The request for Commit.
  • The response for Commit.
  • The request for CreateDatabase.
  • The request for CreateInstance.
  • The request for CreateSession.
  • A Cloud Spanner database.
  • A delegate with a conservative default implementation, which is used if no other delegate is set.
  • Arguments to delete operations.
  • 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:
  • A utility to represent detailed errors we might see in case there are BadRequests. The latter happen if the sent parameters or request structures are unsound
  • The request for ExecuteSql and ExecuteStreamingSql.
  • Represents an expression text. Example:
  • Message representing a single field of a struct.
  • The response for GetDatabaseDdl.
  • Request message for GetIamPolicy method.
  • 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.
  • KeyRange represents a range of rows in a table or index.
  • 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.
  • The response for ListDatabases.
  • The response for ListInstanceConfigs.
  • The response for ListInstances.
  • The response message for Operations.ListOperations.
  • The response for ListSessions.
  • Contains information about an API request.
  • Provides a Read interface that converts multiple parts into the protocol identified by RFC2387. Note: This implementation is just as rich as it needs to be to perform uploads to google APIs, and might not be a fully-featured implementation.
  • 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.
  • This resource represents a long-running operation that is the result of a network API call.
  • 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.
  • Options for a PartitionQueryRequest and PartitionReadRequest.
  • The request for PartitionQuery
  • The request for PartitionRead
  • The response for PartitionQuery or PartitionRead
  • Message type to initiate a Partitioned DML transaction.
  • Node information for nodes appearing in a QueryPlan.plan_nodes.
  • Defines an Identity and Access Management (IAM) policy. It is used to specify access control policies for Cloud Platform resources.
  • Gets information about a particular instance configuration.
  • Lists the supported instance configurations for a given project.
  • Creates an instance and begins preparing it to begin serving. The returned long-running operation can be used to track the progress of preparing the new instance. The instance name is assigned by the caller. If the named instance already exists, CreateInstance returns ALREADY_EXISTS.
  • Creates a new Cloud Spanner database and starts to prepare it for serving. The returned long-running operation will have a name of the format <database_name>/operations/<operation_id> and can be used to track preparation of the database. The metadata field type is CreateDatabaseMetadata. The response field type is Database, if successful.
  • Drops (aka deletes) a Cloud Spanner database.
  • Gets the state of a Cloud Spanner database.
  • Returns the schema of a Cloud Spanner database as a list of formatted DDL statements. This method does not show pending schema updates, those may be queried using the Operations API.
  • Gets the access control policy for a database resource. Returns an empty policy if a database exists but does not have a policy set.
  • Lists Cloud Spanner databases.
  • Starts asynchronous cancellation on a long-running operation. The server makes a best effort to cancel the operation, but success is not guaranteed. If the server doesn’t support this method, it returns google.rpc.Code.UNIMPLEMENTED. Clients can use Operations.GetOperation or other methods to check whether the cancellation succeeded or whether the operation completed despite cancellation. On successful cancellation, the operation is not deleted; instead, it becomes an operation with an Operation.error value with a google.rpc.Status.code of 1, corresponding to Code.CANCELLED.
  • Deletes a long-running operation. This method indicates that the client is no longer interested in the operation result. It does not cancel the operation. If the server doesn’t support this method, it returns google.rpc.Code.UNIMPLEMENTED.
  • Gets the latest state of a long-running operation. Clients can use this method to poll the operation result at intervals as recommended by the API service.
  • Lists operations that match the specified filter in the request. If the server doesn’t support this method, it returns UNIMPLEMENTED.
  • Begins a new transaction. This step can often be skipped: Read, ExecuteSql and Commit can begin a new transaction as a side-effect.
  • Commits a transaction. The request includes the mutations to be applied to rows in the database.
  • Creates a new session. A session can be used to perform transactions that read and/or modify data in a Cloud Spanner database. Sessions are meant to be reused for many consecutive transactions.
  • Ends a session, releasing server resources associated with it.
  • Executes an SQL statement, returning all results in a single reply. This method cannot be used to return a result set larger than 10 MiB; if the query yields more data than that, the query fails with a FAILED_PRECONDITION error.
  • Like ExecuteSql, except returns the result set as a stream. Unlike ExecuteSql, there is no limit on the size of the returned result set. However, no individual row in the result set can exceed 100 MiB, and no column value can exceed 10 MiB.
  • Gets a session. Returns NOT_FOUND if the session does not exist. This is mainly useful for determining whether a session is still alive.
  • Lists all sessions in a given database.
  • Creates a set of partition tokens that can be used to execute a query operation in parallel. Each of the returned partition tokens can be used by ExecuteStreamingSql to specify a subset of the query result to read. The same session and read-only transaction must be used by the PartitionQueryRequest used to create the partition tokens and the ExecuteSqlRequests that use the partition tokens.
  • Creates a set of partition tokens that can be used to execute a read operation in parallel. Each of the returned partition tokens can be used by StreamingRead to specify a subset of the read result to read. The same session and read-only transaction must be used by the PartitionReadRequest used to create the partition tokens and the ReadRequests that use the partition tokens. There are no ordering guarantees on rows returned among the returned partition tokens, or even within each individual StreamingRead call issued with a partition_token.
  • Reads rows from the database using key lookups and scans, as a simple key/value style alternative to ExecuteSql. This method cannot be used to return a result set larger than 10 MiB; if the read matches more data than that, the read fails with a FAILED_PRECONDITION error.
  • Rolls back a transaction, releasing any locks it holds. It is a good idea to call this for any transaction that includes one or more Read or ExecuteSql requests and ultimately decides not to commit.
  • Like Read, except returns the result set as a stream. Unlike Read, there is no limit on the size of the returned result set. However, no individual row in the result set can exceed 100 MiB, and no column value can exceed 10 MiB.
  • Sets the access control policy on a database resource. Replaces any existing policy.
  • Returns permissions that the caller has on the specified database resource.
  • Updates the schema of a Cloud Spanner database by creating/altering/dropping tables, columns, indexes, etc. The returned long-running operation will have a name of the format <database_name>/operations/<operation_id> and can be used to track execution of the schema change(s). The metadata field type is UpdateDatabaseDdlMetadata. The operation has no response.
  • Deletes an instance.
  • Gets information about a particular instance.
  • Gets the access control policy for an instance resource. Returns an empty policy if an instance exists but does not have a policy set.
  • Lists all instances in the given project.
  • Starts asynchronous cancellation on a long-running operation. The server makes a best effort to cancel the operation, but success is not guaranteed. If the server doesn’t support this method, it returns google.rpc.Code.UNIMPLEMENTED. Clients can use Operations.GetOperation or other methods to check whether the cancellation succeeded or whether the operation completed despite cancellation. On successful cancellation, the operation is not deleted; instead, it becomes an operation with an Operation.error value with a google.rpc.Status.code of 1, corresponding to Code.CANCELLED.
  • Deletes a long-running operation. This method indicates that the client is no longer interested in the operation result. It does not cancel the operation. If the server doesn’t support this method, it returns google.rpc.Code.UNIMPLEMENTED.
  • Gets the latest state of a long-running operation. Clients can use this method to poll the operation result at intervals as recommended by the API service.
  • Lists operations that match the specified filter in the request. If the server doesn’t support this method, it returns UNIMPLEMENTED.
  • Updates an instance, and begins allocating or releasing resources as requested. The returned long-running operation can be used to track the progress of updating the instance. If the named instance does not exist, returns NOT_FOUND.
  • Sets the access control policy on an instance resource. Replaces any existing policy.
  • Returns permissions that the caller has on the specified instance resource.
  • A builder providing access to all methods supported on project resources. It is not used directly, but through the Spanner hub.
  • Contains an ordered list of nodes appearing in the query plan.
  • 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.
  • Results from Read or ExecuteSql.
  • Metadata about a ResultSet or PartialResultSet.
  • Additional statistics about a ResultSet or PartialResultSet.
  • The request for Rollback.
  • 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).
  • Central instance to access all Spanner related resource activities
  • 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. The error model is designed to be:
  • StructType defines the fields of a STRUCT type.
  • Request message for TestIamPermissions method.
  • Response message for TestIamPermissions method.
  • A transaction.
  • Transactions
  • This message is used to select the transaction in which a Read or ExecuteSql call runs.
  • Type indicates the type of a Cloud Spanner value, as might be stored in a table cell or returned from an SQL query.
  • 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.
  • The request for UpdateInstance.
  • Arguments to insert, update, insert_or_update, and replace operations.

Enums§

Traits§

  • Identifies types which represent builders for a particular resource method
  • A trait specifying functionality to help controlling any request performed by the API. The trait has a conservative default implementation.
  • Identifies the Hub. There is only one per library, this trait is supposed to make intended use more explicit. The hub allows to access all resource methods more easily.
  • Identifies types for building methods of a particular resource type
  • Identifies types which are only used by other types internally. They have no special meaning, this trait just marks them for completeness.
  • Identifies types which are only used as part of other types, which usually are carrying the Resource trait.
  • A utility to specify reader types which provide seeking capabilities too
  • Identifies types which are used in API requests.
  • Identifies types which can be inserted and deleted. Types with this trait are most commonly used by clients of this API.
  • Identifies types which are used in API responses.
  • A trait for all types that can convert themselves into a parts string

Functions§

Type Aliases§

  • A universal result type used as return for all calls.