-
Bug
-
Resolution: Done
-
Minor
-
1.8.0.Final
-
None
-
False
-
False
-
-
Hi there,
I'm currently running Debezium Server 1.8 with the Oracle Connector. I was trying to implement a workaround to do incremental snapshots on new tables using schema_only_recovery and believe I've come across a bug when using io.debezium.relational.history.FileDatabaseHistory to do a schema_only_recovery.
When I ran a schema_only_recovery, I noticed that nothing was happening. I was not able to reproduce when using a Kafka topic for the history. I've tried logging out messages at various points in the code, and I believe that schema.historyExists in OracleConnectorTask.java will always return true when FileDatabaseHistory is used.
It seems that when the OracleDatabaseSchema object is instantiated, there is a check to see if the file specified exists and if not it creates the file. When historyExists is executed later, it's checking for the file and finds it as it was created in the earlier process