You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
If the incoming schema isn't all lower case (e.g. "MySchema") the code will conclude the tables don't exist and try to recreate them.
To Reproduce
Steps to reproduce the behavior:
Create a schema in MySQL with a mixed-case name (e.g. "MySchema")
Create a table in said schema and put some data in it
Set up a pipeline from MySQL to Postgres and run it. Let target-postgres create the destination schema. This will result in a schema in PG named "myschema"
Add some new data to the table in MySQL.
Re-run the pipeline. target-postgres will log a message saying the table doesn't exist and try to recreate it.
Note that the CREATE TABLE succeeds without error because it includes an IF NOT EXISTS clause. However, if you add a column to your source table the pipeline will fail - because the code thinks the table doesn't exist it tries to create it rather than update the schema.
Expected behavior
The existing table should be recognized, no log message should be generated, and any schema updates should be applied.
Your environment
Version of target: git latest
Version of python 3.8
Meltano latest
The text was updated successfully, but these errors were encountered:
Describe the bug
If the incoming schema isn't all lower case (e.g. "MySchema") the code will conclude the tables don't exist and try to recreate them.
To Reproduce
Steps to reproduce the behavior:
Note that the CREATE TABLE succeeds without error because it includes an IF NOT EXISTS clause. However, if you add a column to your source table the pipeline will fail - because the code thinks the table doesn't exist it tries to create it rather than update the schema.
Expected behavior
The existing table should be recognized, no log message should be generated, and any schema updates should be applied.
Your environment
The text was updated successfully, but these errors were encountered: