-
Notifications
You must be signed in to change notification settings - Fork 982
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add athena ref page #5961
Add athena ref page #5961
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
- `data_cell_filters` management can't be automated outside dbt because the filter can't be attached to the table which doesn't exist. Once you `enable` this config, dbt will set all filters and their permissions during every dbt run. Such approach keeps the actual state of row level security configuration actual after every dbt run and apply changes if they occur: drop, create, update filters and their permissions. | ||
- Any tags listed in `lf_inherited_tags` should be strictly inherited from the database level and never overridden at the table and column level | ||
- Currently `dbt-athena` does not differentiate between an inherited tag association and an override of same it made previously | ||
> - For example, If an inherited tag is overridden by an `lf_tags_config` value in one DBT run, and that override is removed prior to a subsequent run, the prior override will linger and no longer be encoded anywhere (in e.g. Terraform where the inherited value is configured nor in the DBT project where the override previously existed but now is gone) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
> - For example, If an inherited tag is overridden by an `lf_tags_config` value in one DBT run, and that override is removed prior to a subsequent run, the prior override will linger and no longer be encoded anywhere (in e.g. Terraform where the inherited value is configured nor in the DBT project where the override previously existed but now is gone) | |
> - For example, If an inherited tag is overridden by an `lf_tags_config` value in one dbt run, and that override is removed prior to a subsequent run, the prior override will linger and no longer be encoded anywhere (in e.g. Terraform where the inherited value is configured nor in the dbt project where the override previously existed but now is gone) |
The materialization also supports invalidating hard deletes. Check | ||
the [docs](https://docs.getdbt.com/docs/build/snapshots#hard-deletes-opt-in) to understand usage. | ||
|
||
### Working example |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Please delete the working example. I don't think we need it
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
excited to see this new adapter page! here's the first chunk of my review (the Models section and all of its subsections). gonna tackle the Snapshots section next.
|
||
| Parameter | Default | Description | | ||
|-----------|---------|-------------| | ||
| `external_location` | None | The full S3 path to where the table will be saved. Only works with incremental models. Doesn't work with Hive table with `ha` set to `true`. | |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
- sugg: rewording first sentence so it's active voice (vs passive)
- sugg: is the indefinite article missing in the 3rd sentence?
'disabled' as status | ||
``` | ||
|
||
By default, the materialization keeps the last 4 table versions,but you can change it by setting `versions_to_keep`. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
sugg moving this sentence to above the code block. feels like this could get lost in the scanning
|
||
### Update glue data catalog | ||
|
||
Persist resource descriptions as column and relation comments to the glue data catalog, and meta as [glue table properties](https://docs.aws.amazon.com/glue/latest/dg/tables-described.html#table-properties) and [column parameters](https://docs.aws.amazon.com/glue/latest/webapi/API_Column.html). By default, documentation persistence is disabled, but it can be enabled for specific resources or groups of resources as needed. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
i'm having a hard time reading and grokking the first sentence. sugg rewording to improve clarity
sugg updating second sentence to be in active voice
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yeah, I'm struggling here too. @amychen1776 Any ideas on how to clean this thought up?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Maybe something like this:
You can persist your column and model level descriptions to the Glue Data Catalog as glue table properties and column parameters. To enable this, you will need to set the configuration to true as show below.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
here's my review of the H2 Snapshots section and all of its subsections. gonna tackle the next H2.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
last chunk of my review!
Co-authored-by: Ly Nguyen <[email protected]>
Adding description
Co-authored-by: Ly Nguyen <[email protected]>
…etdbt.com into athena-reference
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
What are you changing in this pull request and why?
Adding the Amazon Athena /ref page
Additionally organized the adapter ref page sidebar in alphabetical order
Checklist
Adding or removing pages (delete if not applicable):
website/sidebars.js
website/vercel.json
npm run build
to update the links that point to deleted pages