README.md in embulk-output-bigquery-0.6.0 vs README.md in embulk-output-bigquery-0.6.1

- old
+ new

@@ -35,11 +35,11 @@ | project | string | required unless service\_account's `json_keyfile` is given. | | project\_id | | dataset | string | required | | dataset | | location | string | optional | nil | geographic location of dataset. See [Location](#location) | | table | string | required | | table name, or table name with a partition decorator such as `table_name$20160929`| | auto_create_dataset | boolean | optional | false | automatically create dataset | -| auto_create_table | boolean | optional | true | `false` is available only for `append_direct` mode. Other modes requires `true`. See [Dynamic Table Creating](#dynamic-table-creating) and [Time Partitioning](#time-partitioning) | +| auto_create_table | boolean | optional | true | `false` is available only for `append_direct` mode. Other modes require `true`. See [Dynamic Table Creating](#dynamic-table-creating) and [Time Partitioning](#time-partitioning) | | schema_file | string | optional | | /path/to/schema.json | | template_table | string | optional | | template table name. See [Dynamic Table Creating](#dynamic-table-creating) | | job_status_max_polling_time | int | optional | 3600 sec | Max job status polling time | | job_status_polling_interval | int | optional | 10 sec | Job status polling interval | | is_skip_job_result_check | boolean | optional | false | Skip waiting Load job finishes. Available for append, or delete_in_advance mode | @@ -211,11 +211,11 @@ You can also embed contents of `json_keyfile` at config.yml. ```yaml out: type: bigquery - auth_method: service_account + auth_method: authorized_user json_keyfile: content: | { "client_id":"xxxxxxxxxxx.apps.googleusercontent.com", "client_secret":"xxxxxxxxxxx", @@ -237,11 +237,16 @@ auth_method: compute_engine ``` #### application\_default -Use Application Default Credentials (ADC). +Use Application Default Credentials (ADC). ADC is a strategy to locate Google Cloud Service Account credentials. + +1. ADC checks to see if the environment variable `GOOGLE_APPLICATION_CREDENTIALS` is set. If the variable is set, ADC uses the service account file that the variable points to. +2. ADC checks to see if `~/.config/gcloud/application_default_credentials.json` is located. This file is created by running `gcloud auth application-default login`. +3. Use the default service account for credentials if the application running on Compute Engine, App Engine, Kubernetes Engine, Cloud Functions or Cloud Run. + See https://cloud.google.com/docs/authentication/production for details. ```yaml out: type: bigquery @@ -254,16 +259,16 @@ format to construct table ids. Table ids are formatted at runtime using the local time of the embulk server. For example, with the configuration below, -data is inserted into tables `table_2015_04`, `table_2015_05` and so on. +data is inserted into tables `table_20150503`, `table_20150504` and so on. ```yaml out: type: bigquery - table: table_%Y_%m + table: table_%Y%m%d ``` ### Dynamic table creating There are 3 ways to set schema. @@ -274,11 +279,11 @@ ```yaml out: type: bigquery auto_create_table: true - table: table_%Y_%m + table: table_%Y%m%d schema_file: /path/to/schema.json ``` #### Set template_table in dataset @@ -286,10 +291,10 @@ ```yaml out: type: bigquery auto_create_table: true - table: table_%Y_%m + table: table_%Y%m%d template_table: existing_table_name ``` #### Guess from Embulk Schema