22
33 Description
44 -----------
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.
66
77 This is most commonly used when the structure of a pipeline is static,
88 and its configuration needs to be managed outside the pipeline itself.
99
10- Arguments name must match column name in BigQueryTable
10+ Argument names must match column names in BigQueryTable
1111
1212 Credentials
1313 -----------
@@ -34,7 +34,7 @@ configured Project ID. `BigQuery Data Viewer` role on this project must be grant
3434to read BigQuery data from this project.
3535
3636 ** 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.
3838
3939 ** Table** : Table to read from. A table contains individual records organized in rows.
4040 Each record is composed of columns (also called fields).
@@ -43,9 +43,9 @@ to read BigQuery data from this project.
4343 ** Argument Selection Conditions** : A set of conditions for identifying the arguments to run a pipeline.
4444 A particular use case for this would be feed=marketing; date=20200427.
4545
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.
4747
48- ** Service Account** - service account key used for authorization
48+ ** Service Account** - service account key used for authorization.
4949
5050 * ** File Path** : Path on the local file system of the service account key used for
5151 authorization. Can be set to 'auto-detect' when running on a Dataproc cluster.
0 commit comments