LocalCloud LocalCloud Google Cloud in-a-box
Databases 0 documented workflows

Spanner

Spanner data and administration workflows over gRPC and REST.

Documented workflows

0 workflows

Service boundaries

  • Pinned extended Spanner emulator image; the exact image and immutable digest come from `SPANNER_EMULATOR_IMAGE` in the root Dockerfile.
  • Change-stream support matrix — native gRPC/REST ExecuteStreamingSql supported; official SDK clients through SPANNER_EMULATOR_HOST supported; LocalCloud SQL Editor through managed run APIs or cancellable /query/stream NDJSON supported; gcloud spanner databases execute-sql unsupported for change streams because it uses unary ExecuteSql.
  • Native SQL, read, and streaming read: Local support is not documented. Change-stream reads use native ExecuteStreamingSql. Unary ExecuteSql intentionally retains the emulator's rejection of change-stream queries.
  • Sessions, transactions, and batch DML: Local support is not documented. Existing native transaction and session behavior remains authoritative.
  • Partition query/read and batch write: Local support is not documented. Existing native partition and batch-write behavior remains authoritative.
  • Instance, configuration, and instance-partition administration: Local support is not documented. Existing native instance-admin behavior remains authoritative.
  • Database administration and DDL: Local support is not documented. Existing native database-admin behavior remains authoritative.
  • Instance and database IAM policies: Local support is not documented. Policies are stored durably and returned through native endpoints. Authorization remains intentionally permissive and TestIamPermissions returns requested permissions.
  • Backup, copy, restore, and backup schedules: Local support is not documented. Backups and schedules use LevelDB-backed metadata and compatible long-running operations.
  • Long-running operation lifecycle: Local support is not documented. Native operation polling and lifecycle behavior is shared by instance, database, backup, copy, and restore calls.
  • Ordinary container stop/start retains state; a mounted /var/lib/localcloud volume is required to retain state across container removal or replacement
  • Rows use LevelDB and metadata uses JSON files.
  • Known corruption/recovery risk; internal safety snapshots are not Cloud Spanner Backup API.

Next steps