-
Notifications
You must be signed in to change notification settings - Fork 4
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
feature(hubspot): Company document (requested by Bonfire for Fivetran AI) #24
base: main
Are you sure you want to change the base?
Conversation
@@ -21,7 +21,7 @@ fields as ( | |||
select | |||
{{ | |||
fivetran_utils.fill_staging_columns( | |||
source_columns=adapter.get_columns_in_relation(source('rag_hubspot','contact')), | |||
source_columns=adapter.get_columns_in_relation(source('rag_hubspot','owner')), |
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.
This is an apparent bug fix. Submitted a separate PR for this as well.
@@ -21,15 +21,15 @@ final as ( | |||
'hubspot' as platform, | |||
deal_document.source_relation, | |||
grouped.most_recent_chunk_update, | |||
grouped.chunk_index, | |||
coalesce(grouped.chunk_index, 0) as chunk_index, |
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.
We need this because we're not chunking this object yet, so this is never getting set.
@levonkorganyan are the join/coalesce updates to the I have another PR open and was wondering if I should incorporate those changes into it before merging. |
This PR is for diff purposes only and shouldn't be reviewed for now because it's not up to par for this repo. Fivetran AI is using this branch in its dbt packages instead of the main branch.
Please provide your name and company
Link the issue/feature request which this PR is meant to address
Detail what changes this PR introduces and how this addresses the issue/feature request linked above.
How did you validate the changes introduced within this PR?
Which warehouse did you use to develop these changes?
Did you update the CHANGELOG?
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)
Typically there are additional maintenance changes required before this will be ready for an upcoming release. Are you comfortable with the Fivetran team making a few commits directly to your branch?
If you had to summarize this PR in an emoji, which would it be?
💃
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.
PR Template
Community Pull Request Template (default)
Maintainer Pull Request Template (to be used by maintainers)