07acb46b6f
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
(cherry picked from commit
|
||
|---|---|---|
| .. | ||
| build-proto | ||
| proto | ||
| src | ||
| Cargo.toml | ||
| README.md | ||
| init-bigtable.sh | ||
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:
- Run
gcloud beta emulators bigtable startin the background - Run
$(gcloud beta emulators bigtable env-init)to establish theBIGTABLE_EMULATOR_HOSTenvironment variable - Run
./init-bigtable.shto configure the emulator - 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).