This PR will address the following Issue/Feature: Issue #105
This PR will result in the following new package version:v1.4.1
This will not be a breaking change as we are only adjusting a cte in the fivetran_platform__audit_user_activity model to only parse the JSON data for the actor_email on actor related logs. This should not impact the row counts or results of existing users. Instead this will help reduce compute and ensure there are no JSON parsing issues on historical data.
Please provide the finalized CHANGELOG entry which details the relevant changes included in this PR:
Bug Fixes
Adjusted the fivetran_platform__audit_user_activity model to parse the message_data json field to obtain the actor_email information only if the field contains actor.
This ensures the JSON parsing is only happening on the fields that are relevant. This will help reduce compute and avoid potential JSON parsing errors.
Under the Hood
Included auto-releaser GitHub Actions workflow to automate future releases.
Updated the maintainer PR template to resemble the most up to date format.
PR Checklist
Basic Validation
Please acknowledge that you have successfully performed the following commands locally:
[X] dbt run –full-refresh && dbt test
[X] dbt run (if incremental models are present) && dbt test
Before marking this PR as "ready for review" the following have been applied:
[X] The appropriate issue has been linked, tagged, and properly assigned
[X] All necessary documentation and version upgrades have been applied
[will regenerate after approval] docs were regenerated (unless this PR does not include any code or yml updates)
[x] BuildKite integration tests are passing
[x] Detailed validation steps have been provided below
Detailed Validation
Please share any and all of your validation steps:
Please see the detailed validations provided within the Hex notebook included within the Height ticket. The validations included in the notebook include:
Validation that the row count of the fivetran_platform__audi_user_activity model is the same on both the live version and these changes.
Confirmation that the output of the ctes being modified are the same between both live and changed versions.
If you had to summarize this PR in an emoji, which would it be?
PR Overview
This PR will address the following Issue/Feature: Issue #105
This PR will result in the following new package version:
v1.4.1This will not be a breaking change as we are only adjusting a cte in the
fivetran_platform__audit_user_activitymodel to only parse the JSON data for the actor_email on actor related logs. This should not impact the row counts or results of existing users. Instead this will help reduce compute and ensure there are no JSON parsing issues on historical data.Please provide the finalized CHANGELOG entry which details the relevant changes included in this PR:
Bug Fixes
fivetran_platform__audit_user_activitymodel to parse themessage_datajson field to obtain the actor_email information only if the field containsactor.Under the Hood
PR Checklist
Basic Validation
Please acknowledge that you have successfully performed the following commands locally:
Before marking this PR as "ready for review" the following have been applied:
Detailed Validation
Please share any and all of your validation steps:
Please see the detailed validations provided within the Hex notebook included within the Height ticket. The validations included in the notebook include:
fivetran_platform__audi_user_activitymodel is the same on both the live version and these changes.If you had to summarize this PR in an emoji, which would it be?
🎭