-
Notifications
You must be signed in to change notification settings - Fork 15
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
Allow exclusion of priority data #55
Conversation
@Everettttt thanks for opening this PR! Taking a look at the changes you have proposed, I feel this would be a valuable addition to the package. There is one adjustment that will need to be made in order for the package to properly succeed with this variable. We will need to add the Once the config logic is added to these models to be disabled with the |
I'll do it. |
Thanks so much @Everettttt! Feel free to tag me in the PR and I will be sure to review it as soon as possible once it is open 😄 |
Just realized I'll have to return to this in 2 weeks, though. If this needs doing before then, feel free, but otherwise I'm willing to do it. |
Thanks for the update @Everettttt! 2 weeks will be perfect. There haven't been any other requests at the moment for this to be addressed asap. So that timeline is great. Thanks again 😄 |
Submitted a PR to I'll resolve the conflicts in the present PR tomorrow. |
Conflicts resolved, I hope. Added myself as a contributor to the changelog. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@Everettttt thanks again for putting these PRs together and contributing back to the package 🙌
I made a few minor changes in your branch, but everything looks good to go on my end! I will merge and plan to cut the official releases tomorrow.
What change(s) does this PR introduce?
My team doesn't use Priority in Jira, the API returns nothing from our Priority endpoint, and so source
jira.priority
never gets loaded into the warehouse. Instead, we use custom fields. We still need downstream models likejira__issue_enhanced
, which depend on priority data. This PR allows exclusion of priority data, sojira__issue_enhanced
can get built even if a team lacks priority data.Makes priority data optional. Allows new env var
jira_using_priorities
. Modelsjira__issue_enhanced
andint_jira__issue_join
won't require sourcejira.priority
or contain priority-related columns ifjira_using_priorities: false
.Did you update the CHANGELOG?
Does this PR introduce a breaking change?
Priority data is still used by default (env var
jira_using_priorities: true
indbt_project.yml
).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)
Project versions bumped in both files.
Is this PR in response to a previously created Bug or Feature Request
How did you test the PR changes?
Tested manually with
dbt
CLI (dbt run --select jira_source jira
) from my local machine (Windows 10, PowerShell) to a Redshift warehouse usingdbt-core
1.0.4 anddbt-redshift
1.0.0. All models defined in this repo are built successfully. All models infivetran/jira_source
package exceptstg_jira__priority_tmp
andstg_jira__priority
are built successfully;stg_jira__priority_tmp
throws an error andstg_jira__priority
gets skipped, but this is intentional.Output:
Select which warehouse(s) were used to test the PR