One funny thing with parent child and incremental is the following:
If the replication key is the typical "last_modified" timestamp, what happens if the source system makes changes to the records in the child table and updates the last_modified column in the child table, but the associated parent for that child never reflects the modification in its "last_modified" field in the parent table.
Meltano simply can't know that it should look at the modified children ... because the associated parents were never modified and hence none of the parents child streams even get triggered for sync in the first place.
🤯