* add get_confirmed_blocks_with_data and get_protobuf_or_bincode_cells (cherry picked from commitf3219fb695
) * appease clippy (cherry picked from commit5533e9393c
) * use &[T] instead of Vec<T> where appropriate clippy (cherry picked from commitfbcf6a0802
) * modify get_protobuf_or_bincode_cells to accept and return an iterator (cherry picked from commitf717fda9a3
) * make get_protobuf_or_bincode_cells accept IntoIter on row_keys, make get_confirmed_blocks_with_data return an Iterator (cherry picked from commitd8be0d9430
) Co-authored-by: Edgar Xi <edgarxi97@gmail.com>
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 start
in the background - Run
$(gcloud beta emulators bigtable env-init)
to establish theBIGTABLE_EMULATOR_HOST
environment variable - Run
./init-bigtable.sh
to 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.