fix(luigi/contrib/postgres.py): replace copy_from with copy_expert #3324
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
copy_from
does not accept 'schema.table' notation since psycopg2.9. Then a bug arises in Luigi if the table refers a schema name.This PR modifies the
copy
method behavior, by referingcopy_expert
instead ofcopy_from
, as suggested in psycopg/psycopg2#1294.Motivation and Context
I'm trying to insert some data into a table that is stored into a specific schema (which is not the
public
schema), and remain stucked at this stage. See #3198 for details.Have you tested this? If so, how?
Design the following task class and run
luigi --local-scheduler --module fulltablename InsertIntoDB
:Fix #3198