Update fivetran_platform__audit_user_activity.sql #107
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
PR Overview
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
fivetran_platform__audit_user_activity
model to parse themessage_data
json 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_activity
model 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?
🎭