Denis I.
10/18/2023, 9:22 PMLOG_BASED
replication from Postgres to Postgres (both transferwise variant) and faced some issues:
1. _sdc_deleted_at
column works as expected, but everything other than PK
seems `NULL`ed in the target table after deletion from the source table. Is there a way to keep values before deletion?
2. When a new table created in source DB, it totally ignored by the tap. meltano invoke tap-postgres --discover
outputs the new table metadata. Looks like it never rewrites .meltano/run/tap.properties.json
file. Removing .meltano
folder and following reinstall helps to see the new table with meltano select tap-postgres --list
command, but every time I execute run
command the tap keeps doing initial FULL_TABLE
load and doesn’t update state (which stored in Postgres by meltano) to start using LOG_BASED
. Doing meltano state clear
helps, but it starts FULL_TABLE
for every previously added tables. Is there something that I’m missing?Denis I.
10/18/2023, 9:22 PM- name: tap-postgres
variant: transferwise
pip_url: pipelinewise-tap-postgres
config:
filter_schemas: public
default_replication_method: LOG_BASED
debug_lsn: true
itersize: 20000
break_at_end_lsn: true
metadata:
"*":
replication-method: LOG_BASED
- name: target-postgres
variant: transferwise
pip_url: pipelinewise-target-postgres
config:
add_metadata_columns: true
primary_key_required: true
hard_delete: false
batch_size_rows: 20000
Denis I.
10/19/2023, 11:12 AMFULL_TABLE
and removes the new table from state.
At the same time tap.properties.json
has the new table.Denis I.
10/19/2023, 12:06 PMDenis I.
10/19/2023, 8:46 PMМарта Сакаль
02/09/2024, 11:33 AMDenis I.
02/09/2024, 12:21 PM