Skip to content
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

Merged

Commits on Jan 19, 2021

  1. Fix JdbcSource handling of tables with same names in different schemas

    * 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.
    cgardens committed Jan 19, 2021
    Configuration menu
    Copy the full SHA
    ec78ae4 View commit details
    Browse the repository at this point in the history

Commits on Jan 20, 2021

  1. bump versions

    cgardens committed Jan 20, 2021
    Configuration menu
    Copy the full SHA
    6470fc2 View commit details
    Browse the repository at this point in the history
  2. fix redshift versions

    cgardens committed Jan 20, 2021
    Configuration menu
    Copy the full SHA
    2f0b34b View commit details
    Browse the repository at this point in the history