docs(destination-bigquery): update BigQuery destination docs#78303
Draft
devin-ai-integration[bot] wants to merge 1 commit into
Draft
docs(destination-bigquery): update BigQuery destination docs#78303devin-ai-integration[bot] wants to merge 1 commit into
devin-ai-integration[bot] wants to merge 1 commit into
Conversation
Contributor
Author
🤖 Devin AI EngineerI'll be helping with this pull request! Here's what you should know: ✅ I will automatically:
Note: I can only respond to comments from users who have write access to this repository. ⚙️ Control Options:
|
Contributor
👋 Greetings, Airbyte Team Member!Here are some helpful tips and reminders for your convenience. 💡 Show Tips and TricksPR Slash CommandsAirbyte Maintainers (that's you!) can execute the following slash commands on your PR:
📚 Show Repo GuidanceHelpful Resources
|
devin-ai-integration
Bot
added
area/documentation
Contributor
|
Deploy preview for airbyte-docs ready!
Deployed with vercel-action |
devin-ai-integration
Bot
force-pushed
the
docs/auto/destination-bigquery
branch
from
0dadf02 to
83f39b9
Compare
![github-actions[bot]](https://avatars.githubusercontent.com/in/15368?s=60&v=4){kind=small}
| you see networking or memory management problems with the sync (specifically on the | ||
| destination), try decreasing the chunk size. In that case, the sync will be slower but more | ||
| likely to succeed. | ||
| 10. For **CDC deletion mode**, choose how the destination handles delete records from CDC sources. |
Contributor
There was a problem hiding this comment.
[markdownlint] reported by reviewdog 🐶
MD029/ol-prefix Ordered list item prefix [Expected: 1; Actual: 10; Style: 1/2/3]
| 10. For **CDC deletion mode**, choose how the destination handles delete records from CDC sources. | ||
| **Hard delete** propagates source deletes to the destination table. **Soft delete** keeps the | ||
| row and records the delete marker. | ||
| 11. Optional: expand **Advanced** to configure **Legacy raw tables** or **Airbyte Internal Table |
Contributor
There was a problem hiding this comment.
[markdownlint] reported by reviewdog 🐶
MD029/ol-prefix Ordered list item prefix [Expected: 2; Actual: 11; Style: 1/2/3]
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.
Triggering Context
Run triggered by: API User requested the
!connectordocsplaybook fordestination-bigqueryafter merged connector commit c03d43d.Relevant context: Commit c03d43d came from merged PR #78333, which promoted
destination-bigquery3.0.19 from release candidate to main version and disabled progressive rollout.Confidence impact: The trigger was a small merged release-promotion PR with clear scope, so the triggering-context score is high.
Documentation Confidence Assessment
Overall Confidence: 2/5 capped: too much code inference
What I Verified vs. What I Inferred
project_id,dataset_location,dataset_id,loading_method,credentials_json,cdc_deletion_mode,disable_type_dedupe, andraw_data_dataset; supported destination sync modes are overwrite, append, and append dedup; GCS staging uses HMAC credentials, a bucket name, a bucket path, and a temp-file post-processing option; the connector can create datasets and runs BigQuery load/query jobs; PR chore: cut release. #78333 promoted 3.0.19 and disabled progressive rollout.Areas of Concern
docs/integrations/destinations/bigquery-migrations.mdbecause the triggering change did not introduce or modify a breaking change.auto-mergelabel because the confidence score is 2/5.What
Updates the BigQuery destination documentation after reviewing connector commit c03d43d and recent connector source changes.
Reviewers: this is an AI-proposed documentation update based on recent
destination-bigquerychanges. You can merge this PR, modify it, or close it if you disagree with the proposed docs.How
Review guide
docs/integrations/destinations/bigquery.mdsetup guidance for removed configuration fields.docs/integrations/destinations/bigquery.mdnew Reference section and GCS Staging example.docs/integrations/destinations/bigquery.mdchangelog entries for 3.0.19 and 3.0.19-rc.1.User Impact
Users get more accurate setup guidance for BigQuery permissions, loading methods, CDC deletion mode, advanced settings, and programmatic configuration. The changelog now points the 3.0.19 release entry to the release-promotion PR that introduced it.
Can this PR be safely reverted and rolled back?
Devin session