Merge pull request #102 from fivetran/bug/audit-user-activity-test-grain

fix grain of user audit activity model

CHANGELOG.md

@@ -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 🚨

models/fivetran_platform.yml

@@ -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.
@@ -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.