Summary
Inquiry about maintaining cursor in connection state for incremental parent stream to avoid reading the whole parent stream since the initial date and reading the child stream for each returned parent row.
Question
Is there a way to use an incremental parent stream and maintain the current cursor in the connection state? The use case is that I want to hit an API that returns a single object based on an ID returned in the parent incremental stream. The result I get is that the parent stream always gets an empty cursor and doesn’t save the cursor in the connection state after the sync is complete. The effect is that it always reads the whole parent stream since the initial date and reads the child stream for each returned parent row. Am I doing something wrong or this sort of setup is just not supported?
This topic has been created from a Slack thread to give it more visibility.
It will be on Read-Only mode here. Click here if you want to access the original thread.