-
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
Nested columns are not written by normalization #1896
Comments
When I run the source connector, here is one output record (it contains the missing fields):
And when I
this point to the issue being a normalization problem. |
This is blocked on #1491 |
Nested columns are not supported by normalization as reported here: #886 |
removing the bug tag on this one as it is not currently supported. @ChristopheDuong i think the stuff you're work is going to add this feature, right should we close it as duplicate or is there any additional info on here that you need? |
We probably should keep them open and review the test cases one by one to validate that normalization is indeed working well with various sources. For example, at this point the unnesting normalization seems to pass successfully on Facebook and Stripe sources but is failing on Hubspot: Re-working the name collisions and making sure the table name is not too long may help in solving this one: Upgrading DBT to version 19 will also give us more room on tables name length for postgres:
|
This is now better handled in normalization, closing it |
Expected Behavior
I expect the Hubspot source connector to replicate contact properties from my Hubspot CRM.
Current Behavior
This was the table that was written to postgres with normalization:
which is a very small subset of the properties available from the
contacts
stream. The full schema of the stream is listed in this gist (it's too big to display inline here).Steps to Reproduce
The text was updated successfully, but these errors were encountered: