update history staging models with correct active records

[fivetran-reneeli]

PR Overview

This PR will address the following Issue/Feature:
#3

This PR will result in the following new package version:
v0.1.1

This will update records for customers going forward

Please provide the finalized CHANGELOG entry which details the relevant changes included in this PR:

PR #4 contains the following updates:

• Updates the filtering done in the history staging models to pull the correct active statuses. Since some changes are entered but not yet effective, we needed to replace the _fivetran_active filter to where current timestamp is between _fivetran_start and _fivetran_end times for each record.

PR Checklist

Basic Validation

Please acknowledge that you have successfully performed the following commands locally:

• dbt run –full-refresh && dbt test
• dbt run (if incremental models are present) && dbt test

Before marking this PR as "ready for review" the following have been applied:

• The appropriate issue has been linked, tagged, and properly assigned.
• All necessary documentation and version upgrades have been applied.
• docs were regenerated (unless this PR does not include any code or yml updates).
• BuildKite integration tests are passing.
• Detailed validation steps have been provided below.

Detailed Validation

Please share any and all of your validation steps:

linked in height!

If you had to summarize this PR in an emoji, which would it be?

📖

[fivetran-reneeli]

• regen docs

[fivetran-joemarkiewicz]

@fivetran-reneeli this looks great! The only thing holding me back from approving is the question around the use of the current_timestamp_backcompat macro. Would you be able to look into my remaining question and let me know if this is still necessary or if we should switch to using current_timestamp.

Once you come to an answer I can re-review and approve.

[fivetran-joemarkiewicz]

@fivetran-reneeli thanks for looking into the remaining questions and applying the appropriate updates. This looks good to go with one last suggestion to update the CHANGELOG with the additional changes.

After that this is good to have docs regen'd and the release review process initiated.