-
Notifications
You must be signed in to change notification settings - Fork 975
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
Update databricks-configs.md for merge settings #6682
base: current
Are you sure you want to change the base?
Conversation
@benc-db is attempting to deploy a commit to the dbt-labs Team on Vercel. A member of the Team first needs to authorize it. |
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
- `not_matched_by_source_condition`: Condition to apply to the further filter `WHEN NOT MATCHED BY SOURCE` clause. Only used in conjunction with `not_matched_by_source_action: delete`. | ||
- `not_matched_by_source_action`: If set to `delete`, a `DELETE` clause is added to the merge statement for `WHEN NOT MATCHED BY SOURCE`. | ||
- `not_matched_by_source_condition`: Condition to apply to the further filter `WHEN NOT MATCHED BY SOURCE` clause. Only used in conjunction with `not_matched_by_source_action`. | ||
- `not_matched_by_source_action`: Action to apply when the condition is met. For example: `update set t.attr1 = 'deleted', t.tech_change_ts = current_timestamp()`. |
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.
@benc-db This wording is unclear to me. Is this a boolean field or one that takes inputs like delete (and maybe others?)
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.
It takes an expression, like the example.
@amychen1776 I've approved the editorial review but wanted to ensure your query was satisfied before merging. |
What are you changing in this pull request and why?
1.9.1 dbt-databricks added a missed merge option, where you can update rows on non-match. Updating the docs to cover it.
Checklist