Feature/v2 updates

[fivetran-jamie]

Pull Request
Are you a current Fivetran customer?

fivetran made PR

What change(s) does this PR introduce?

• adds line item, campaign, and account report tables
• adds tweet table as well
• incorporates passthrough columns into report tables
• adds schema tests to all staging models
• aligns promoted_tweet_report model with the other report models
• updates README
• documents new tables and columns
• incorporate identifier variables
• TODO AFTER APPROVING: regen docs

Did you update the CHANGELOG?

• Yes

Does this PR introduce a breaking change?

• Yes (please provide breaking change details below.)
• No (please provide an explanation as to how the change is non-breaking below.)

Did you update the dbt_project.yml files with the version upgrade (please leverage standard semantic versioning)? (In both your main project and integration_tests)

• Yes

Is this PR in response to a previously created Bug or Feature Request

• Yes, Issue/Feature [link bug/feature number here]
• No

How did you test the PR changes?

• CircleCi
• Local (please provide additional testing details below)

Select which warehouse(s) were used to test the PR

• BigQuery
• Redshift
• Snowflake
• Postgres
• Databricks
• Other (provide details below)

Provide an emoji that best describes your current mood

🍏

Feedback

We are so excited you decided to contribute to the Fivetran community dbt package! We continue to work to improve the packages and would greatly appreciate your feedback on our existing dbt packages or what you'd like to see next.

[fivetran-joemarkiewicz]

@fivetran-jamie thanks for this PR! There definitely was a lot added to this package, thanks for working though all of these updates! 🙌

The PR looks great, I just had a few inline comments to be addressed as well as a few thoughts I would like your insight on before approving. See inline comments for more details.

[fivetran-joemarkiewicz]

@fivetran-jamie updates look great!! Only request is to move the disabling docs to the required section of the README opposed to the additional.

Once we make that update we will be good to hold this PR until all others are ready to merge.

[fivetran-joemarkiewicz]

@fivetran-jamie one last thing I noticed was that the date_day field for the reports seemed to report on different hours each day. Is this regular? I would imagine the date_day field to simple display the date and not an hour of the day?

[fivetran-jamie]

@fivetran-jamie one last thing I noticed was that the date_day field for the reports seemed to report on different hours each day. Is this regular? I would imagine the date_day field to simple display the date and not an hour of the day?

good catch -- yeah i think date_trunc'ing date_day in the staging models is the best move