Conversation
github-actions
bot
added
content
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
| | `INFORMATION_SCHEMA.PARTITIONS` | Partition information | Dataset only | | ||
| | `__TABLES__` (deprecated) | Table modification times | Dataset | | ||
|
|
||
| ### BigQuery DataFrames (optional) {#bigquery-dataframes} |
| | `CREATE SCHEMA` | Database | Fusion should auto-create schemas | | ||
| | `CREATE DATABASE` | Account | Fusion should auto-create databases | | ||
|
|
||
| ### Advanced features |
There was a problem hiding this comment.
the table with the auth fields under the callout (snowflake column size changes) falls under 'advanced features' but it's teh same as the table at the beginning under 'required snowflake objects https://docs-getdbt-com-git-adapter-perms-dbt-labs.vercel.app/docs/cloud/connect-data-platform/connect-snowflake?version=1.12#required-snowflake-objects? is that a little confusing?
There was a problem hiding this comment.
Yeah, that's sort of by design - this section is saying these objects must exist for the project connection to work. I added a header to the section below the callout to make it more apparent, but what do you think. Should I remove the section here?
|
|
||
| ### Fusion engine warehouse privileges | ||
|
|
||
| When projects run on the <Constant name="fusion_engine" /> (Fusion CLI or a Fusion-supported connection on the <Constant name="dbt_platform" />), use the **Warehouse permissions** sections in the Fusion adapter setup guides for detailed privilege tables: |
There was a problem hiding this comment.
for readers unfamiliar with fusion, we might want to have a brief intro or link to fusion.
also should we mention the dbt vsce as well? i wonder if just saying fusion cli or fusion supported connection on platform is clear enough for users? maybe:
Use these warehouse permissions if you're running dbt on the — either using the Fusion CLI or dbt VS Code extension locally, or a connection on .
Refer to the Warehouse permissions sections in the adapter setup guides for detailed privilege tables:
|
|
||
| When projects run on the <Constant name="fusion_engine" /> (Fusion CLI or a Fusion-supported connection on the <Constant name="dbt_platform" />), use the **Warehouse permissions** sections in the Fusion adapter setup guides for detailed privilege tables: | ||
|
|
||
| - [Snowflake](/docs/fusion/connect-data-platform-fusion/snowflake-setup#warehouse-permissions) |
There was a problem hiding this comment.
i'm sure you know this but the links here aren't in the sidebar.js file - is that known?
There was a problem hiding this comment.
Oh crud, pulled in the wrong ones. Need to delete those old Fusion docs. Good catch!
| | `roles/bigquery.user` | Run jobs, create datasets | Job execution | | ||
| | `roles/bigquery.jobUser` | Run jobs only | Minimal query execution | | ||
|
|
||
| For Storage Read API access with Fusion, also grant **BigQuery Read Session User** (`roles/bigquery.readSessionUser`) on the project, as noted in [Connect BigQuery](/docs/cloud/connect-data-platform/connect-bigquery#required-permissions). |
There was a problem hiding this comment.
heads up there is no required permissions. did we mean https://docs-getdbt-com-git-adapter-perms-dbt-labs.vercel.app/docs/cloud/connect-data-platform/about-connections?version=2.0#supported-authentication-methods?
There was a problem hiding this comment.
if so, should update the tabs so fusion is first one this page?
| - gcloud OAuth | ||
|
|
||
| ## BigQuery permissions | ||
| ## Warehouse permissions |
There was a problem hiding this comment.
small nit but i noticed we have a fusion compatible badge for versions older than 2.0 - should we have it visible for all versions so it's consistent with the platform bq page (which has the badge visible for all versions)?
There was a problem hiding this comment.
Yeah, I can update that in a separate PR
|
couple of questions/non blockers and approved @matthewshaver ! |
Co-authored-by: Mirna Wong <89008547+mirnawong1@users.noreply.github.com>
3 participants
What are you changing in this pull request and why?
Closes jira https://dbtlabs.atlassian.net/browse/PRODDOCS-502
Checklist
🚀 Deployment available! Here are the direct links to the updated files: