* 1.made load_credentials accept credential path as a parameter. 2.partial implement bigtable comparasion function
* finding missing blocks in bigtables in a specified range
* refactor compare-blocks,add unit test for missing_blocks and fmt
* compare-block fix last block bug
* refactor compare-block and improve wording
* Update ledger-tool/src/bigtable.rs
Co-authored-by: Tyera Eulberg <teulberg@gmail.com>
* update compare-block command-line description
* style:improve wording/naming/code style
Co-authored-by: Tyera Eulberg <teulberg@gmail.com>
(cherry picked from commit d9220652ad)
Co-authored-by: pieceofr <komimi.p@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 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.