Hi there,
I wanted to ask about a use case we have in our organisation and whether this could be something Debezium might cater for in the future.
We've deployed Debezium on a few databases and our plan is to replace our existing ingestion processes with it over time. Currently we use Streamsets along with a trigger-based solution to perform change data capture on most of our databases.
Something that would be useful would be if it were possible to configure Debezium to be able to to use a LAST_UPDATE_TIME or some similar incrementing column instead of log-based change data capture. This would allow us to transition to using Debezium in our existing environments without having to make changes on the source system.
It'd be useful to be able to have this as a potential config for the various connectors (or maybe it'd be a generic standalone jdbc connector?). I imagine the mechanism would be similar to the sort of polling done for SQL Servers CDC. I know this goes against the principle of Debezium using log-based replication and so I wanted to find out if this was something Debezium would consider implementing?