runako_godfrey
07/21/2025, 3:39 PMINSERT
statements are now include the new column, which PostgreSQL doesn't like. (The new column does not appear in the schema generated by meltano invoke <my tap> --discover
, which is correct.)
Is there a way to tell Meltano/target-postgres to only include in its generated SQL columns that appear in the Meltano schema?
Thanks in advance!visch
07/21/2025, 4:31 PMrunako_godfrey
07/21/2025, 5:46 PMversion: 1
default_environment: dev
project_id: <obfuscated>
plugins:
extractors:
- name: tap-customer-spreadsheets-anywhere
inherit_from: tap-spreadsheets-anywhere
variant: ets
pip_url: git+<https://github.com/><my_fork>/tap-spreadsheets-anywhere.git
config:
tables:
- path: sftp://<obfuscated>
name: my_table
pattern: .*\.xlsx
start_date: "2025-04-10T00:00:00Z"
key_properties:
- user_id
- group_id
schema_overrides:
user_id:
type: ["null", string]
format: detect
universal_newlines: false
sample_rate: 10
max_sampling_read: 2000
max_sampled_files: 3
prefer_number_vs_integer: true
selected: true
loaders:
- name: target-postgres
variant: meltanolabs
pip_url: git+<https://github.com/healthrosetta/target-postgres.git>
config:
database: mydb
default_target_schema: dest
host: <obfuscated>
port: 5432
user: meltano
stream_maps:
this_is_the_relevant_stream:
source_file_date: __NULL__
runako_godfrey
07/21/2025, 5:47 PMsource_file_date
is the generated column. I tried without that stream map, and it also did not work.