Hey team, I had a question regarding `ignore_paren...
# singer-tap-development
s
Hey team, I had a question regarding
ignore_parent_replication_keys=True
Here is what we currently have • Parent stream:
Contacts
, with a primary key (id) and a replication key (updated_at) • Child stream:
Association_contacts_deals
, with a primary key contact_id-deal_id and no replication key ◦ Since the features of this API call are only an id and a label, this stream is always
FULL_TABLE
ignore_parent_replication_key
is set to true From my understanding,
ignore_parent_replication_key
means that a child stream will get updated, even when the parent has not changed PROBLEM: Currently, our child value is only updating if the associated parent value is updated Question: • I am I right in my understanding of
ignore_parent_replication_key
• If yes, then what could be stopping my table from fully replicating? Note: We are not directly loading into bigquery, but are passing by Stitch, which could possibly be a source of error