Opt-in: --services spanner,bigtable
Spanner and Bigtable emulators, with a console that can query them.
Instances, databases, DDL and queries on Spanner; tables, column families and rows on Bigtable. Google's emulators, opt-in.
Backed by: Google's Spanner emulator 1.5.58 and Bigtable emulator Google's emulator
In the console
What it covers
Spanner and Bigtable run on Google’s own emulators and start with --services. The console has a read-only SQL editor for Spanner and a query builder for Bigtable. Both are in memory.
- Spanner instances, databases, DDL, reads, writes and SQL queries
- Bigtable tables, column families and rows
- Read-only SQL editor for Spanner and a query builder for Bigtable in the console
What's verified
Spanner
Not in v0.1.0's coverage table.
10 of 65 RPCs Verified on main next release
Bigtable
Not in v0.1.0's coverage table.
6 of 50 RPCs Verified on main next release
Not supported
- In memory: nothing survives a restart, whatever
--modesays - Other methods are Unknown: served by Google's emulator, not yet driven by a test, so not claimed
Source: docs/compatibility.md at main 82a2eb9.
Questions
Is Spanner data persisted?
No. Both emulators are in memory, and this is measured for Spanner: after a pod restart the data is gone.
Link to this answer
Build against Google Cloud APIs, locally
Free and open source under Apache-2.0. No account, no sign-up, no Google Cloud bill.