2
2
3
3
Description
4
4
-----------
5
- Performs an BigQueryTable Query request to fetch arguments to set in the pipeline.
5
+ Performs a BigQueryTable Query request to fetch arguments to set in the pipeline.
6
6
7
7
This is most commonly used when the structure of a pipeline is static,
8
8
and its configuration needs to be managed outside the pipeline itself.
9
9
10
- Arguments name must match column name in BigQueryTable
10
+ Argument names must match column names in BigQueryTable
11
11
12
12
Credentials
13
13
-----------
@@ -34,7 +34,7 @@ configured Project ID. `BigQuery Data Viewer` role on this project must be grant
34
34
to read BigQuery data from this project.
35
35
36
36
** Dataset Name** : Dataset the table belongs to. A dataset is contained within a specific project.
37
- Datasets are top-level containers that are used to organize and control access to tables and views.
37
+ Datasets are top-level containers used to organize and control access to tables and views.
38
38
39
39
** Table** : Table to read from. A table contains individual records organized in rows.
40
40
Each record is composed of columns (also called fields).
@@ -43,9 +43,9 @@ to read BigQuery data from this project.
43
43
** Argument Selection Conditions** : A set of conditions for identifying the arguments to run a pipeline.
44
44
A particular use case for this would be feed=marketing; date=20200427.
45
45
46
- ** Arguments Columns** : Name of the columns, separated by comma that contains the arguments for this run
46
+ ** Arguments Columns** : Name of the columns, separated by commas, that contains the arguments for this run.
47
47
48
- ** Service Account** - service account key used for authorization
48
+ ** Service Account** - service account key used for authorization.
49
49
50
50
* ** File Path** : Path on the local file system of the service account key used for
51
51
authorization. Can be set to 'auto-detect' when running on a Dataproc cluster.
0 commit comments