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.
What's the fix?
Add PII info (email, username, name) to dim_teachers and make underlying staging model incremental.
Why?
Marketing is often needing to pull teacher email addresses (and sometimes names) based on whether or not they still use code.org. Our models would allow them to do this if these PII fields were added to dim_teachers. This PII is already made available to them (and the org) through various google sheets, so was approved by Travis to be user-facing in Trevor. No PII is in the code itself.