-
Notifications
You must be signed in to change notification settings - Fork 4.3k
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
Postgres source: verify handling of arrays data types #15157
Comments
The first step here is to create an E2E test scenario with Postgres Source and any GA destination (e.g., pick one GA destination) with a source data set that has various arrays. The goal of the test is to confirm if (and which) source arrays will break syncs with Postgres Source. |
Implementation details:
|
We should definitely not crash, but I'm not clear on the goal here. is it to support arrays (with any subtype) or render them as a string? @misteryeo @grishick @subodh1810 |
@edgao and @VitaliiMaltsev met earlier this week about Vitalii's proposal. The goal is to support arrays as arrays and not render them as strings. |
Current Behavior
Adding fields to a table that are not of the expected data type in Postgres will result in unexpected failures as shown here
Expected Behavior
Data type handling should be able to handle all data types that Postgres supports
Logs
Steps to Reproduce
Are you willing to submit a PR?
Addressable points are that there needs to be an enforcement of the inclusion of
"items"
for any"array"
type stream as referenced hereInitial PR that attempted to address this issue and add an included
items
but only for string data types within theJsonSchema.ARRAY
The text was updated successfully, but these errors were encountered: