Formatting

metadata-ingestion/source_docs/bigquery.md

@@ -88,26 +88,24 @@ source:
     bucket_duration: "DAY"
 
     top_n_queries: 10
-
-
 ```
 
 ## Config details
 
 Note that a `.` is used to denote nested fields in the YAML recipe.
 
-| Field                  | Required | Default                                                      | Description                                                  |
-| ---------------------- | -------- | ------------------------------------------------------------ | ------------------------------------------------------------ |
-| `projects`             |          |                                                              |                                                              |
-| `extra_client_options` |          |                                                              |                                                              |
-| `env`                  |          | `"PROD"`                                                     | Environment to use in namespace when constructing URNs.      |
-| `bucket_duration`      |          | `"DAY"`                                                      | Duration to bucket usage events by. Can be `"DAY"` or `"HOUR"`. |
-| `start_time`           |          | Last full day in UTC (or hour, depending on `bucket_duration`) | Earliest date of usage logs to consider.                     |
-| `end_time`             |          | Last full day in UTC (or hour, depending on `bucket_duration`) | Latest date of usage logs to consider.                       |
-| `top_n_queries`        |          | `10`                                                         | Number of top queries to save to each table.                 |
-| `extra_client_options` |          |                                                              | Additional options to pass to `google.cloud.logging_v2.client.Client`. |
-| `query_log_deplay`     |          |                                                              | To account for the possibility that the query event arrives after the read event in the audit logs, we wait for at least `query_log_delay` additional events to be processed before attempting to resolve BigQuery job information from the logs. If `query_log_delay` is `None`, it gets treated as an unlimited delay, which prioritizes correctness at the expense of memory usage. |
-| `max_query_duration`   |          | `15`                                                         | Correction to pad `start_time` and `end_time` with. For handling the case where the read happens within our time range but the query completion event is delayed and happens after the configured end time. |
+| Field                  | Required | Default                                                        | Description                                                                                                                                                                                                                                                                                                                                                                            |
+| ---------------------- | -------- | -------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `projects`             |          |                                                                |                                                                                                                                                                                                                                                                                                                                                                                        |
+| `extra_client_options` |          |                                                                |                                                                                                                                                                                                                                                                                                                                                                                        |
+| `env`                  |          | `"PROD"`                                                       | Environment to use in namespace when constructing URNs.                                                                                                                                                                                                                                                                                                                                |
+| `bucket_duration`      |          | `"DAY"`                                                        | Duration to bucket usage events by. Can be `"DAY"` or `"HOUR"`.                                                                                                                                                                                                                                                                                                                        |
+| `start_time`           |          | Last full day in UTC (or hour, depending on `bucket_duration`) | Earliest date of usage logs to consider.                                                                                                                                                                                                                                                                                                                                               |
+| `end_time`             |          | Last full day in UTC (or hour, depending on `bucket_duration`) | Latest date of usage logs to consider.                                                                                                                                                                                                                                                                                                                                                 |
+| `top_n_queries`        |          | `10`                                                           | Number of top queries to save to each table.                                                                                                                                                                                                                                                                                                                                           |
+| `extra_client_options` |          |                                                                | Additional options to pass to `google.cloud.logging_v2.client.Client`.                                                                                                                                                                                                                                                                                                                 |
+| `query_log_deplay`     |          |                                                                | To account for the possibility that the query event arrives after the read event in the audit logs, we wait for at least `query_log_delay` additional events to be processed before attempting to resolve BigQuery job information from the logs. If `query_log_delay` is `None`, it gets treated as an unlimited delay, which prioritizes correctness at the expense of memory usage. |
+| `max_query_duration`   |          | `15`                                                           | Correction to pad `start_time` and `end_time` with. For handling the case where the read happens within our time range but the query completion event is delayed and happens after the configured end time.                                                                                                                                                                            |
 
 ## Questions