🐛 Source Hubspot: add TypeTransformer to Tickets stream
#38286
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎ 1 Ignored Deployment
|
octavia-squidington-iii
added
the
area/documentation
tolik0
approved these changes
May 16, 2024
cmm-airbyte
approved these changes
May 16, 2024
maxi297
reviewed
May 16, 2024
|
@maxi297 Could you please refer to this conversation? |
|
Not sure how to chalk this up to user error, but it definitely was showing as an option in 4.1.3 and not in 4.1.4. Now it is showing agian... |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What
Having this issue:
There is an issue with the Hubspot source. The nightly tests failed because the contacts in the tickets stream are of the wrong type. The expected type is an integer, but we are getting a string for our test account.
How
TypeTransformerwith default schema normalization to ensure the declared data types, declared in stream schemaUser Impact
No impact is expected.
Can this PR be safely reverted and rolled back?