Skip to content

docs: document read-only input mapping for BigQuery transformations#1016

Open
romanbracinik wants to merge 3 commits into
mainfrom
romanbracinik-dmd-1739-bigquery-transformations-document-read-only-storage-input
Open

docs: document read-only input mapping for BigQuery transformations#1016
romanbracinik wants to merge 3 commits into
mainfrom
romanbracinik-dmd-1739-bigquery-transformations-document-read-only-storage-input

Conversation

@romanbracinik

Copy link
Copy Markdown
Contributor

What

Adds a Bucket Objects for Read-Only Input Mapping section to the BigQuery transformations page, on par with the existing Snowflake section.

  • Uses the BigQuery dataset model: in.c-main → dataset in_c_main; <branchId>_in_c_* in dev branches.
  • How to reference tables (fully qualified backtick names) and linked buckets (qualify with the source project ID).
  • Dev tip: create a workspace with read-only input mappings enabled to discover project/dataset names.
  • New subsection on branch read isolation (ships with DMD-1699): a dev-branch workspace reads its own branch + default datasets; other branches are denied; a default-branch workspace reads only default datasets.
  • Does not copy the Snowflake "dev branches share the same schema as production" caveat — it is Snowflake-specific and false for BigQuery.
  • Fixes the BigQuery link on the mappings page to point at the new anchor.

Verification

  • npm run build clean.
  • node scripts/audit-phase2.mjs: no new broken links (3 pre-existing, unrelated).

Closes DMD-1739

Add a Bucket Objects for Read-Only Input Mapping section to the BigQuery
transformations page, mirroring the Snowflake one, using the BigQuery
dataset model (in_c_* default, <branchId>_in_c_* in dev branches).
Includes a branch read-isolation note and links from the mappings page.

DMD-1739
@linear-code

linear-code Bot commented Jul 13, 2026

Copy link
Copy Markdown

DMD-1739

@vercel

vercel Bot commented Jul 13, 2026

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
connection-docs Ready Ready Preview, Comment Jul 13, 2026 4:53pm

Request Review

@keboola-pr-reviewer-bot keboola-pr-reviewer-bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Verdict: needs_human (risk 2/5) · profile docs

Escalate — new BigQuery section introduces product-behaviour claims that need product-team confirmation.

Concerns:

  • src/content/docs/transformations/bigquery/index.md: New unverifiable product-behaviour claims (dataset naming, alias VIEWs, linked-bucket refs)
  • src/content/docs/transformations/bigquery/index.md: Dev-branch read-isolation behaviour documented as shipping with an unreleased ticket

Suggested reviewers: @keboola/docs

@jordanrburger

Copy link
Copy Markdown
Contributor

Review summary

Verdict: merge-ready pending one release check.

Clean, well-structured — mirrors the existing Snowflake "Bucket Objects for Read-Only Input Mapping" section for BigQuery. Frontmatter/markdown intact, correct location (transformations/bigquery/index.md), and the anchor fix on the mappings page resolves correctly (#bucket-objects-for-read-only-input-mapping).

Before publishing:

  • The "Read-Only Input Mapping in Development Branches" subsection documents behavior the PR body says "ships with DMD-1699." Confirm that ticket is actually released at/before merge — otherwise this documents unreleased behavior.

Product-behavior claims (dataset naming in_c_main, alias VIEWs, linked-bucket project-ID qualification, INFORMATION_SCHEMA.SCHEMATA) come from an engineer and mirror the Snowflake section, so they're plausible — a product sign-off is the right gate since they can't be verified from the diff.

Automated review pass (Claude Code), flagged for a human maintainer — not an approval.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants