Open shippy opened 6 months ago
The good folks from Meltano Slack have helped me narrow down the issue to this section of the code - if I'm reading this right, the code fails not because there are two primary keys, but because there are zero non-primary keys?
Ah that makes sense? What would be the right thing to do in that case?
Still write the new primary keys, I guess? I haven't actually eval'd the code to make sure that the resulting SQL is broken, though.
Describe the bug I'm not 100% sure what is happening here. A table in tap-mysql has two columns, each of which is a primary key. target-duckdb creates a corresponding table with two primary keys, successfully creates a temp table with the full contents in
main
schema, then fails when copying it into the target schema.The failure is
duckdb.duckdb.ParserException: Parser Error: syntax error at or near "FROM"
, but I'm unable to get at the exact expression being executed. The full traceback follows:Removing the primary keys from the MySQL table of origin is an effective workaround for the issue, which makes me think that the primary keys are to blame.
To Reproduce Steps to reproduce the behavior:
run tap-mysql target-duckdb
Expected behavior A table is successfully replicated in DuckDB, with or without primary keys.
Screenshots If applicable, add screenshots to help explain your problem.
Your environment
meltano/meltano:latest
DockerAdditional context