solana/storage-bigtable
Tyera 166be2995e
Bigtable: update google proto files and allow configuration of max_message_size (#34740)
* Update proto files with tonic-build v0.9.2

* Manually ignore invalid doc-tests

* Add new ReadRowsRequest fields

* Add LedgerStorageConfig::max_message_size and default value

* Add BigtableConnection::max_message_size and use on client creation

* Add max_message_size to RpcBigtableConfig and make const pub

* Add solana-validator cli arg
2024-01-10 21:20:15 -07:00
..
build-proto chore: workspace inheritance (#29893) 2023-02-23 22:01:54 +08:00
proto Bigtable: update google proto files and allow configuration of max_message_size (#34740) 2024-01-10 21:20:15 -07:00
src Bigtable: update google proto files and allow configuration of max_message_size (#34740) 2024-01-10 21:20:15 -07:00
Cargo.toml chore: workspace inheritance (#29893) 2023-02-23 22:01:54 +08:00
README.md bigtable: allow forward proxy in gRPC connection (#25918) 2022-06-23 10:51:31 -06:00
init-bigtable.sh storage-bigtable: Upload entries (#34099) 2023-11-28 11:47:22 -07:00

README.md

BigTable Setup

Development Environment

The Cloud BigTable emulator can be used during development/test. See https://cloud.google.com/bigtable/docs/emulator for general setup information.

Process:

  1. Run gcloud beta emulators bigtable start in the background
  2. Run $(gcloud beta emulators bigtable env-init) to establish the BIGTABLE_EMULATOR_HOST environment variable
  3. Run ./init-bigtable.sh to configure the emulator
  4. Develop/test

Production Environment

Export a standard GOOGLE_APPLICATION_CREDENTIALS environment variable to your service account credentials. The project should contain a BigTable instance called solana-ledger that has been initialized by running the ./init-bigtable.sh script.

Depending on what operation mode is required, either the https://www.googleapis.com/auth/bigtable.data or https://www.googleapis.com/auth/bigtable.data.readonly OAuth scope will be requested using the provided credentials.

Forward proxy

Export BIGTABLE_PROXY environment variable for the forward proxy as you would for HTTP_PROXY. This will establish a tunnel through the forward proxy for gRPC traffic (the tunneled traffic will still use TLS as normal).