Loading...

XML

Word

Printable

Details

Type: Bug
Resolution: Done
Priority: Minor
Fix Version/s: 1.9.0.Alpha2
Affects Version/s: 1.8.0.Final
Component/s: debezium-server, oracle-connector
Labels:
None

Blocked:
False
Ready:
False
Target Release:

1.9.GA
Steps to Reproduce:

Hide

1) Set history settings something like the below:

debezium.source.database.history.file.filename=data/file_database_history
debezium.source.database.history=io.debezium.relational.history.FileDatabaseHistory

2) Run initial snapshot

3) Stop debezium server

4) Change snapshot.mode to schema_only_recovery

5) Start up Debezium server. Schema recovery doesn't run

Show
1) Set history settings something like the below: debezium.source.database.history.file.filename=data/file_database_history debezium.source.database.history=io.debezium.relational.history.FileDatabaseHistory 2) Run initial snapshot 3) Stop debezium server 4) Change snapshot.mode to schema_only_recovery 5) Start up Debezium server. Schema recovery doesn't run

SFDC Cases Counter:
SFDC Cases Links:

Description

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