Elgato_dark/zeppelin
1
0
Fork 0
mirror of https://github.com/apache/zeppelin synced 2026-05-24 09:38:26 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions 1

Fix typos in docs

Browse source
This commit is contained in:
Alexander Bezzubov 2016-07-30 08:59:29 +09:00
parent 03a777f31e
commit 64525b8979
1 changed files with 2 additions and 2 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

4
docs/interpreter/bigquery.md
View file

@ -46,7 +46,7 @@ In a notebook, to enable the **BigQuery** interpreter, click the **Gear** icon a
### Setup service account credentials
In order to run BigQuery interpreter outside of Google Cloud Engine you need to provide authentification crednetials,
In order to run BigQuery interpreter outside of Google Cloud Engine you need to provide authentication credentials,
by [following this instructions](https://developers.google.com/identity/protocols/application-default-credentials):
- Go to the [API Console Credentials page](https://console.developers.google.com/project/_/apis/credentials)
@ -54,7 +54,7 @@ by [following this instructions](https://developers.google.com/identity/protocol
- On the `Credentials` page, select the `Create credentials` drop-down, then select `Service account key`.
- From the Service account drop-down, select an existing service account or create a new one.
- For `Key type`, select the `JSON` key option, then select `Create`. The file automatically downloads to your computer.
- Put the *.json file you just downloaded in a directory of your choosing. This directory must be private (you can't let anyone get access to this), but accessible to your Zeppelin instance.
- Put the `*.json` file you just downloaded in a directory of your choosing. This directory must be private (you can't let anyone get access to this), but accessible to your Zeppelin instance.
- Set the environment variable `GOOGLE_APPLICATION_CREDENTIALS` to the path of the JSON file downloaded.
* either though GUI: in interpreter configuration page property names in CAPITAL_CASE set up env vars
* or though `zeppelin-env.sh`: just add it to the end of the file.