From 03a777f31e935910dbc3d9fa6e086144200f8287 Mon Sep 17 00:00:00 2001 From: Alexander Bezzubov Date: Fri, 29 Jul 2016 15:41:57 +0900 Subject: [PATCH 1/2] add docs for BigQuery auth outside of GCE --- docs/interpreter/bigquery.md | 15 +++++++++++++++ 1 file changed, 15 insertions(+) diff --git a/docs/interpreter/bigquery.md b/docs/interpreter/bigquery.md index 99c4d3029e3..5e6cdd7352a 100644 --- a/docs/interpreter/bigquery.md +++ b/docs/interpreter/bigquery.md @@ -44,6 +44,21 @@ Zeppelin is built against BigQuery API version v2-rev265-1.21.0 - [API Javadocs] In a notebook, to enable the **BigQuery** interpreter, click the **Gear** icon and select **bigquery**. +### Setup service account credentials + +In order to run BigQuery interpreter outside of Google Cloud Engine you need to provide authentification crednetials, +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) + - From the project drop-down, select your project. + - 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. + - 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. + ## Using the BigQuery Interpreter In a paragraph, use `%bigquery.sql` to select the **BigQuery** interpreter and then input SQL statements against your datasets stored in BigQuery. From 64525b89799ad6f189011f30e5aa78f3c9ff28f4 Mon Sep 17 00:00:00 2001 From: Alexander Bezzubov Date: Sat, 30 Jul 2016 08:59:29 +0900 Subject: [PATCH 2/2] Fix typos in docs --- docs/interpreter/bigquery.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/interpreter/bigquery.md b/docs/interpreter/bigquery.md index 5e6cdd7352a..1e92aa98757 100644 --- a/docs/interpreter/bigquery.md +++ b/docs/interpreter/bigquery.md @@ -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.