You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+26-2Lines changed: 26 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -112,6 +112,12 @@ Following options are same as [bq command-line tools](https://cloud.google.com/b
112
112
| time_partitioning.type | string | required | nil | The only type supported is DAY, which will generate one partition per day based on data loading time. |
113
113
| time_partitioning.expiration_ms | int | optional | nil | Number of milliseconds for which to keep the storage for a partition. |
114
114
| time_partitioning.field | string | optional | nil |`DATE` or `TIMESTAMP` column used for partitioning |
| range_partitioning.field | string | required | nil |`INT64` column used for partitioning |
117
+
| range-partitioning.range | hash | required | nil | Defines the ranges for range paritioning |
118
+
| range-partitioning.range.start | int | required | nil | The start of range partitioning, inclusive. |
119
+
| range-partitioning.range.end | int | required | nil | The end of range partitioning, exclusive. |
120
+
| range-partitioning.range.interval| int | required | nil | The width of each interval. |
115
121
| clustering | hash | optional | nil | Currently, clustering is supported for partitioned tables, so must be used with `time_partitioning` option. See [clustered tables](https://cloud.google.com/bigquery/docs/clustered-tables)|
116
122
| clustering.fields | array | required | nil | One or more fields on which data should be clustered. The order of the specified columns determines the sort order of the data. |
117
123
| schema_update_options | array | optional | nil | (Experimental) List of `ALLOW_FIELD_ADDITION` or `ALLOW_FIELD_RELAXATION` or both. See [jobs#configuration.load.schemaUpdateOptions](https://cloud.google.com/bigquery/docs/reference/v2/jobs#configuration.load.schemaUpdateOptions). NOTE for the current status: `schema_update_options` does not work for `copy` job, that is, is not effective for most of modes such as `append`, `replace` and `replace_backup`. `delete_in_advance` deletes origin table so does not need to update schema. Only `append_direct` can utilize schema update. |
@@ -332,8 +338,8 @@ Column options are used to aid guessing BigQuery schema, or to define conversion
0 commit comments