-
Notifications
You must be signed in to change notification settings - Fork 4.2k
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
Source Hubspot: fix for property_history
stream
#13596
Source Hubspot: fix for property_history
stream
#13596
Conversation
…ich did not emit any records
/test connector=connectors/source-hubspot
Build FailedTest summary info:
|
Codecov Report
@@ Coverage Diff @@
## master #13596 +/- ##
=========================================
Coverage ? 90.57%
=========================================
Files ? 5
Lines ? 912
Branches ? 0
=========================================
Hits ? 826
Misses ? 86
Partials ? 0 Continue to review full report at Codecov.
|
/test connector=connectors/source-hubspot
Build PassedTest summary info:
|
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.
thank you @davydov-d this is great!
airbyte-integrations/connectors/source-hubspot/acceptance-test-config.yml
Show resolved
Hide resolved
airbyte-integrations/connectors/source-hubspot/source_hubspot/helpers.py
Outdated
Show resolved
Hide resolved
airbyte-integrations/connectors/source-hubspot/source_hubspot/helpers.py
Outdated
Show resolved
Hide resolved
/test connector=connectors/source-hubspot
Build PassedTest summary info:
|
/publish connector=connectors/source-hubspot
|
What
PopertyHistory
stream did not emit any recordshttps://github.com/airbytehq/oncall/issues/259
How
versions
field we use to yield records from. That's becausepropertyMode
was not explicitly set - now fixed. Methodlist
, which was probably designed for it, was never used, so I dropped it.property
was for some reason namedproperties
and the values were passed separated with commas instead of&
. Now fixed, it allows us to get more detailed response.entity
attribute was not set. Now fixed.denormalize_records
attribute for that).property_history
used to be of typedate-time
(although originally this field is of type timestamp in the API) what led to buggy behavior when reading incrementally. Rolled back the field type, changed the schema.