Skip to content
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.

Sign up for GitHub

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

fix grain of user audit activity model #102

Merged
merged 3 commits into from
Dec 7, 2023
Merged

fix grain of user audit activity model #102

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
438c47a
fix grain of user audit activity model
fivetran-jamie Dec 4, 2023
c809ead
changelog with pr link
fivetran-jamie Dec 5, 2023
8ad1cfb
Update CHANGELOG.md
fivetran-jamie Dec 7, 2023
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
7 changes: 7 additions & 0 deletions CHANGELOG.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,3 +1,10 @@
# dbt_fivetran_log v1.3.1

## Bug Fixes
[PR #102](https://github.com/fivetran/dbt_fivetran_log/pull/102) applies the following update:
- Adjusts the uniqueness test on the recently introduced `fivetran_platform__audit_user_activity` model to test on `log_id` and `occurred_at`.
- Previously, the `log_id` was erroneously considered the primary key of this model.

# dbt_fivetran_log v1.3.0

## 🚨 Breaking Changes 🚨
Expand Down
10 changes: 6 additions & 4 deletions models/fivetran_platform.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -287,6 +287,11 @@ models:
Each record represents a user-triggered action in your Fivetran instance.This model is intended for audit-trail purposes, as it can be very helpful
when trying to trace a user action to a [log event](https://fivetran.com/docs/logs#logeventlist) such as a schema change, sync frequency update,
manual update, broken connection, etc.
tests:
- dbt_utils.unique_combination_of_columns:
combination_of_columns:
- log_id
- occurred_at
columns:
- name: date_day
description: Date on which the user action occurred.
Expand Down Expand Up @@ -323,7 +328,4 @@ models:
- name: message_data
description: The details of the event in JSON format.
- name: log_id
description: Unique ID of the log record.
tests:
- unique
- not_null
description: Unique ID of the log record.