Document optional BigQuery Location field - #39764
Open
lisaah wants to merge 1 commit into
Open
Conversation
Contributor
|
I can only run on private repositories. |
Contributor
Preview links (active after the
|
drichards-87
approved these changes
Sep 8, 2026
brett0000FF
approved these changes
Sep 8, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What does this PR do? What is the motivation?
Documents the new optional Location field in the BigQuery warehouse connection settings for Datadog Experiments, added in https://github.com/ddoghq/dd-source/pull/78991.
Customers whose BigQuery dataset lives in a non-default region need a way to tell Datadog where to submit experiment queries. This adds that field to the existing setup steps.
Changes:
## Step 3: Configure experiment settingsinhugo/content/en/experiments/guide/connecting_a_data_warehouse.mdoc.md.europe-west2), that Datadog submits experiment queries in that location, and that leaving it blank lets BigQuery infer the location.Testing:
Field (optional):convention used by the Copy IAM role ARN field in the Redshift branch, and the[Step 1](#create-a-bigquery-dataset)anchor already used by the sibling Dataset field.CLAUDE.md(noensure,via,just,will,currently, and so on). Vale is not installed in this environment, so this check was manual.{% if equals($database, "bigquery") %}block and does not affect the Databricks, Redshift, or Snowflake branches.Merge readiness
For Datadog employees:
<name>/<description>convention and include the forward slash (/). If you've already created your PR with an incorrect branch name, please rename your branch and open a fresh PR./reviewto run an automated check that catches common issues before a Documentation team member reviews your PR.AI assistance
Drafted with Bits Code, then reviewed against the page's existing field-list conventions and the repo style guide.
Additional notes
The field label is documented as Location, matching the short labels used by the sibling Dataset and GCS Bucket fields. Please confirm this matches the label shipped in the UI.
PR by Bits - View session in Datadog
Comment @DataDog to request changes