Skip to content

Commit 994e8c9

Browse files
authored
fix admonition rendering for bq (#37730)
1 parent d26a3ba commit 994e8c9

File tree

1 file changed

+19
-9
lines changed

1 file changed

+19
-9
lines changed

docs/integrations/destinations/bigquery.md

+19-9
Original file line numberDiff line numberDiff line change
@@ -80,13 +80,21 @@ https://github.com/airbytehq/airbyte/issues/3549
8080
4. Enter the name for the BigQuery connector.
8181
5. For **Project ID**, enter your
8282
[Google Cloud project ID](https://cloud.google.com/resource-manager/docs/creating-managing-projects#identifying_projects).
83-
6. For **Dataset Location**, select the location of your BigQuery dataset. :::warning You cannot
84-
change the location later. :::
83+
6. For **Dataset Location**, select the location of your BigQuery dataset.
84+
85+
:::warning
86+
You cannot change the location later.
87+
:::
88+
8589
7. For **Default Dataset ID**, enter the BigQuery
8690
[Dataset ID](https://cloud.google.com/bigquery/docs/datasets#create-dataset).
8791
8. For **Loading Method**, select [Standard Inserts](#using-insert) or
88-
[GCS Staging](#recommended-using-a-google-cloud-storage-bucket). :::tip We recommend using the
89-
GCS Staging option. :::
92+
[GCS Staging](#recommended-using-a-google-cloud-storage-bucket).
93+
94+
:::tip
95+
We recommend using the GCS Staging option.
96+
:::
97+
9098
9. For **Service Account Key JSON (Required for cloud, optional for open-source)**, enter the Google
9199
Cloud
92100
[Service Account Key in JSON format](https://cloud.google.com/iam/docs/creating-managing-service-account-keys).
@@ -95,11 +103,13 @@ https://github.com/airbytehq/airbyte/issues/3549
95103
or **batch** to have
96104
[BigQuery run batch queries](https://cloud.google.com/bigquery/docs/running-queries#batch).
97105

98-
:::note Interactive queries are executed as soon as possible and count towards daily concurrent
99-
quotas and limits, while batch queries are executed as soon as idle resources are available in
100-
the BigQuery shared resource pool. If BigQuery hasn't started the query within 24 hours,
101-
BigQuery changes the job priority to interactive. Batch queries don't count towards your
102-
concurrent rate limit, making it easier to start many queries at once. :::
106+
:::note
107+
Interactive queries are executed as soon as possible and count towards daily concurrent
108+
quotas and limits, while batch queries are executed as soon as idle resources are available in
109+
the BigQuery shared resource pool. If BigQuery hasn't started the query within 24 hours,
110+
BigQuery changes the job priority to interactive. Batch queries don't count towards your
111+
concurrent rate limit, making it easier to start many queries at once.
112+
:::
103113

104114
11. For **Google BigQuery Client Chunk Size (Optional)**, use the default value of 15 MiB. Later, if
105115
you see networking or memory management problems with the sync (specifically on the

0 commit comments

Comments
 (0)