gaspersic/solana
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity
Files
4ee366edfa2dada9ade18dc204306c6f94d1e270
solana/storage-bigtable
History
mergify[bot] 4ee366edfa Properly handle block_height in Bigtable bincode deserialization (#17990) (#17994) 
* Default block_height on eof

* Add comment to prevent future errors

(cherry picked from commit c57d1b44ef)

Co-authored-by: Tyera Eulberg <teulberg@gmail.com>
2021-06-16 05:41:38 +00:00
..
build-proto
Bump version to v1.7.2 (#17831)
2021-06-08 10:29:39 +00:00
proto
Bump tonic, prost, tarpc, tokio (#15013)
2021-02-05 00:21:53 -07:00
src
Properly handle block_height in Bigtable bincode deserialization (#17990) (#17994)
2021-06-16 05:41:38 +00:00
Cargo.toml
Bump version to v1.7.2 (#17831)
2021-06-08 10:29:39 +00:00
init-bigtable.sh
Add configuration info
2020-08-05 14:27:12 -07:00
README.md
Add configuration info
2020-08-05 14:27:12 -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.