Skip to content

Commit e8b3090

Browse files
authored
Apply suggestions from code review
1 parent 7c222eb commit e8b3090

File tree

1 file changed

+3
-5
lines changed

1 file changed

+3
-5
lines changed

src/connections/reverse-etl/reverse-etl-source-setup-guides/bigquery-setup.md

Lines changed: 3 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -83,11 +83,9 @@ You can find the location of your BigQuery resources using the following method:
8383
11. Click **Test Connection** to test to see if the connection works. If the connection fails, make sure you have the right permissions and credentials and try again.
8484
12. If the test connection completes successfully, click **Add source** to complete the setup process.
8585
86-
When setting up a BigQuery Reverse ETL source, you can choose which API Segment uses to read from BigQuery. You can make this selection during the initial setup, or later from Sources > Reverse ETL > BigQuery Source > Settings > Connection Settings.
87-
- **REST API**
88-
Recommended for most tables. REST is generally more cost-efficient, but syncs may be slower for very large datasets.
89-
- **Storage API**
90-
Recommended for large tables. The Storage API can significantly improve throughput and reduce sync times, but may incur higher costs. See [BigQuery Storage API client libraries](https://cloud.google.com/bigquery/docs/reference/storage/libraries) and [BigQuery pricing for data extraction](https://cloud.google.com/bigquery/pricing?hl=en#data_extraction_pricing) for more information
86+
When setting up a BigQuery Reverse ETL source, you can choose which API Segment uses to read from BigQuery. You can make this selection during the initial setup, or later from **Connections > Sources > Reverse ETL > BigQuery Source > Settings > Connection Settings**. You can choose from:
87+
- **REST API**: This is recommended for most tables. REST is generally more cost-efficient, but syncs may be slower for very large datasets.
88+
- **Storage API**: This is recommended for large tables. The Storage API can significantly improve throughput and reduce sync times, but may incur higher costs. See [BigQuery Storage API client libraries](https://cloud.google.com/bigquery/docs/reference/storage/libraries) and [BigQuery pricing for data extraction](https://cloud.google.com/bigquery/pricing?hl=en#data_extraction_pricing){:target="_blank"} for more information.
9189
9290
9391
After you've added BigQuery as a source, you can [add a model](/docs/connections/reverse-etl/setup/#step-2-add-a-model) and follow the rest of the steps in the Reverse ETL setup guide.

0 commit comments

Comments
 (0)