-
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
Fix JdbcSource handling of tables with same names in different schemas #1724
Fix JdbcSource handling of tables with same names in different schemas #1724
Conversation
* Previously the JdbcSource was combining the columns of any tables with the same name across different schemas into a single stream in the catalog. * This was caught because in those tables there were columns of the same name with different types which triggered a precondition to check for this. * The fix makes sure we group by both schema name and table name. * Adds test to the standard jdbc tests to catch this case. * This test does NOT run for mysql as, mysql has no concept of schemas.
e90be05
to
ec78ae4
Compare
/test connector=destination-postgres
|
/test connector=source-postgres
|
/test connector=source-mssql
|
/test connector=source-mysql
|
/test connector=source-redshift
|
Closes Unable to exit onboarding - Stuck on "Set up connection" in #1684
Previously the JdbcSource was combining the columns of any tables with the same name across different schemas into a single stream in the catalog.
This was caught because in those tables there were columns of the same name with different types which triggered a precondition to check for this.
The fix makes sure we group by both schema name and table name.
Adds test to the standard jdbc tests to catch this case.
This test does NOT run for mysql as, mysql has no concept of schemas.
Checklist