Created new section called Parallel batch execution #6589
Merged
Conversation
This file contains 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
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
github-actions
bot
added
content
nataliefiann
commented
Dec 4, 2024
mirnawong1
reviewed
Dec 4, 2024
mirnawong1
reviewed
Dec 4, 2024
mirnawong1
reviewed
Dec 4, 2024
mirnawong1
reviewed
Dec 4, 2024
Co-authored-by: Mirna Wong <[email protected]>
mirnawong1
reviewed
Dec 4, 2024
Co-authored-by: Mirna Wong <[email protected]>
mirnawong1
reviewed
Dec 4, 2024
Co-authored-by: Mirna Wong <[email protected]>
mirnawong1
reviewed
Dec 4, 2024
Co-authored-by: Mirna Wong <[email protected]>
Co-authored-by: Mirna Wong <[email protected]>
Co-authored-by: Mirna Wong <[email protected]>
mirnawong1
reviewed
Dec 4, 2024
mirnawong1
reviewed
Dec 4, 2024
|
hey @nataliefiann , good job! it's getting there -- remember you still want to add this to the:
|
Co-authored-by: Mirna Wong <[email protected]>
mirnawong1
reviewed
Dec 4, 2024
nataliefiann
commented
Dec 4, 2024
nataliefiann
commented
Dec 6, 2024
nataliefiann
commented
Dec 6, 2024
…and added links to incremental microbatch page (#6608) ## What are you changing in this pull request and why? I've created this PR to show updates to upgrading to v1.9 guide to included parallel batch execution and added links to incremental microbatch page ## Checklist - [ ] I have reviewed the [Content style guide](https://github.com/dbt-labs/docs.getdbt.com/blob/current/contributing/content-style-guide.md) so my content adheres to these guidelines. - [ ] The topic I'm writing about is for specific dbt version(s) and I have versioned it according to the [version a whole page](https://github.com/dbt-labs/docs.getdbt.com/blob/current/contributing/single-sourcing-content.md#adding-a-new-version) and/or [version a block of content](https://github.com/dbt-labs/docs.getdbt.com/blob/current/contributing/single-sourcing-content.md#versioning-blocks-of-content) guidelines. - [ ] I have added checklist item(s) to this list for anything anything that needs to happen before this PR is merged, such as "needs technical review" or "change base branch." - [ ] The content in this PR requires a dbt release note, so I added one to the [release notes page](https://docs.getdbt.com/docs/dbt-versions/dbt-cloud-release-notes). <!-- PRE-RELEASE VERSION OF dbt (if so, uncomment): - [ ] Add a note to the prerelease version [Migration Guide](https://github.com/dbt-labs/docs.getdbt.com/tree/current/website/docs/docs/dbt-versions/core-upgrade) --> <!-- ADDING OR REMOVING PAGES (if so, uncomment): - [ ] Add/remove page in `website/sidebars.js` - [ ] Provide a unique filename for new pages - [ ] Add an entry for deleted pages in `website/vercel.json` - [ ] Run link testing locally with `npm run build` to update the links that point to deleted pages --> <!-- vercel-deployment-preview --> --- 🚀 Deployment available! Here are the direct links to the updated files: - https://docs-getdbt-com-git-new-branch-name-1-dbt-labs.vercel.app/docs/build/incremental-microbatch - https://docs-getdbt-com-git-new-branch-name-1-dbt-labs.vercel.app/docs/dbt-versions/core-upgrade/06-upgrading-to-v1.9 <!-- end-vercel-deployment-preview --> --------- Co-authored-by: Mirna Wong <[email protected]> Co-authored-by: Leona B. Campbell <[email protected]>
## What are you changing in this pull request and why? I've created a new page to describe how the concurrent batches config works ## Checklist - [ ] I have reviewed the [Content style guide](https://github.com/dbt-labs/docs.getdbt.com/blob/current/contributing/content-style-guide.md) so my content adheres to these guidelines. - [ ] The topic I'm writing about is for specific dbt version(s) and I have versioned it according to the [version a whole page](https://github.com/dbt-labs/docs.getdbt.com/blob/current/contributing/single-sourcing-content.md#adding-a-new-version) and/or [version a block of content](https://github.com/dbt-labs/docs.getdbt.com/blob/current/contributing/single-sourcing-content.md#versioning-blocks-of-content) guidelines. - [ ] I have added checklist item(s) to this list for anything anything that needs to happen before this PR is merged, such as "needs technical review" or "change base branch." - [ ] The content in this PR requires a dbt release note, so I added one to the [release notes page](https://docs.getdbt.com/docs/dbt-versions/dbt-cloud-release-notes). <!-- PRE-RELEASE VERSION OF dbt (if so, uncomment): - [ ] Add a note to the prerelease version [Migration Guide](https://github.com/dbt-labs/docs.getdbt.com/tree/current/website/docs/docs/dbt-versions/core-upgrade) --> <!-- ADDING OR REMOVING PAGES (if so, uncomment): - [ ] Add/remove page in `website/sidebars.js` - [ ] Provide a unique filename for new pages - [ ] Add an entry for deleted pages in `website/vercel.json` - [ ] Run link testing locally with `npm run build` to update the links that point to deleted pages --> <!-- vercel-deployment-preview --> --- 🚀 Deployment available! Here are the direct links to the updated files: - https://docs-getdbt-com-git-new-branch-name-dbt-labs.vercel.app/docs/build/incremental-microbatch - https://docs-getdbt-com-git-new-branch-name-dbt-labs.vercel.app/docs/core/connect-data-platform/mssql-setup - https://docs-getdbt-com-git-new-branch-name-dbt-labs.vercel.app/docs/dbt-versions/core-upgrade/06-upgrading-to-v1.9 - https://docs-getdbt-com-git-new-branch-name-dbt-labs.vercel.app/reference/resource-properties/concurrent_batches <!-- end-vercel-deployment-preview --> --------- Co-authored-by: Mirna Wong <[email protected]> Co-authored-by: Leona B. Campbell <[email protected]>
runleonarun
requested changes
Dec 6, 2024
runleonarun
reviewed
Dec 6, 2024
runleonarun
reviewed
Dec 6, 2024
runleonarun
approved these changes
Dec 7, 2024
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 are you changing in this pull request and why?
I have created this PR following this Git issue: #6550 for Parallel batch execution
Checklist
🚀 Deployment available! Here are the direct links to the updated files: