-
Notifications
You must be signed in to change notification settings - Fork 4.5k
feat(source-hubspot): incremental streams to low code: email_events, engagements, subscription_changes #58592
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
feat(source-hubspot): incremental streams to low code: email_events, engagements, subscription_changes #58592
Conversation
The latest updates on your projects. Learn more about Vercel for Git βοΈ
|
regression tests:test_catalog_are_the_same[failed] new fields added: |
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.
nice work on the engagements
stream which is definitely on the trickier side. I did leave some comments around the contact_lists
stream that I want to clarify before we move forward since this one may have some changes that impact users due to the switch from the v1 to v3 endpoint.
airbyte-integrations/connectors/source-hubspot/source_hubspot/manifest.yaml
Outdated
Show resolved
Hide resolved
airbyte-integrations/connectors/source-hubspot/source_hubspot/manifest.yaml
Outdated
Show resolved
Hide resolved
airbyte-integrations/connectors/source-hubspot/source_hubspot/manifest.yaml
Outdated
Show resolved
Hide resolved
airbyte-integrations/connectors/source-hubspot/source_hubspot/manifest.yaml
Outdated
Show resolved
Hide resolved
airbyte-integrations/connectors/source-hubspot/source_hubspot/manifest.yaml
Show resolved
Hide resolved
airbyte-integrations/connectors/source-hubspot/source_hubspot/components.py
Outdated
Show resolved
Hide resolved
airbyte-integrations/connectors/source-hubspot/source_hubspot/components.py
Show resolved
Hide resolved
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.
lgtm! thank you for the detailed explanation about the EngagementsHttpRequester
. I thought about how we could try to define _use_recent_api
when we instantiate the requester up front, but didn't see a good way since we need to know the start_time
.
Either way, looks good with the latest regression test run. π’
airbyte-integrations/connectors/source-hubspot/source_hubspot/components.py
Show resolved
Hide resolved
|
/format-fix
|
What
How
Review guide
User Impact
Can this PR be safely reverted and rolled back?