-
Notifications
You must be signed in to change notification settings - Fork 105
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
feat(DENG-7899): fx_accounts_active_daily_clients_v1 #7078
Conversation
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
Hi-- The only thing I am curious about is if we can a) in This is because for stakeholders, understanding OS and OS versions will be critical in understanding account profiles. |
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
Good idea - I pulled windows_build_number out of the nested field into its own column. I also added a column to the view called "os_version_build" which basically helps distinguish Windows 10 vs 11 based on build #, and then for all other things, it's just the concatenation of normalized OS and normalized OS version. We can always adjust the view later on as needed in a subsequent PR to adjust this logic |
Integration report for "Add column to view"
|
Description
This PR creates the new table and associated view:
Related Tickets & Documents
Reviewer, please follow this checklist