com.google.cloud.spanner

Interface Spanner

All Superinterfaces:

Service<SpannerOptions>

public interface Spanner
extends Service<SpannerOptions>

An interface for Cloud Spanner. Typically, there would only be one instance of this for the lifetime of the application which must be closed by invoking close() when it is no longer needed. Failure to do so may result in leaking session resources and exhausting session quota.

Method Summary

Modifier and Type	Method and Description
void	close() Closes all the clients associated with this instance and frees up all the resources.
DatabaseAdminClient	getDatabaseAdminClient() Returns a DatabaseAdminClient to do admin operations on Cloud Spanner databases.
DatabaseClient	getDatabaseClient(DatabaseId db) Returns a DatabaseClient for the given database.
InstanceAdminClient	getInstanceAdminClient() Returns an InstanceAdminClient to do admin operations on Cloud Spanner instances.

Methods inherited from interface com.google.cloud.Service

getOptions

Method Detail

getDatabaseAdminClient

DatabaseAdminClient getDatabaseAdminClient()

Returns a DatabaseAdminClient to do admin operations on Cloud Spanner databases.

getInstanceAdminClient

InstanceAdminClient getInstanceAdminClient()

Returns an InstanceAdminClient to do admin operations on Cloud Spanner instances.

getDatabaseClient

DatabaseClient getDatabaseClient(DatabaseId db)

Returns a DatabaseClient for the given database. It uses a pool of sessions to talk to the database.

close

void close()

Closes all the clients associated with this instance and frees up all the resources. This method will block until it can clean up all the resources. Specifically, it deletes all the underlying sessions (which involves rpcs) and closes all the gRPC channels. Once this method called, this object is no longer usable. It is strongly advised to call this method when you are done with the Spanner object, typically when your application shuts down. There is a hard limit on number of sessions in Cloud Spanner and not calling this method can lead to unused sessions piling up on the backend.