From 2e4be4c5ee6a6bebcf8d831b6ae7fc2dfedcb751 Mon Sep 17 00:00:00 2001
From: Jiri Pechanec <jpechane@redhat.com>
Date: Tue, 13 Feb 2018 05:08:19 +0100
Subject: [PATCH] DBZ-278 Create topic only when needed

---
 .../java/io/debezium/connector/mysql/MySqlConnectorTask.java    | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/debezium-connector-mysql/src/main/java/io/debezium/connector/mysql/MySqlConnectorTask.java b/debezium-connector-mysql/src/main/java/io/debezium/connector/mysql/MySqlConnectorTask.java
index 0683158f9..5ff9b5ece 100644
--- a/debezium-connector-mysql/src/main/java/io/debezium/connector/mysql/MySqlConnectorTask.java
+++ b/debezium-connector-mysql/src/main/java/io/debezium/connector/mysql/MySqlConnectorTask.java
@@ -79,7 +79,6 @@ public synchronized void start(Map<String, String> props) {
 
                 // First check if db history is available
                 if (!taskContext.historyExists()) {
-                    taskContext.initializeHistoryStorage();
                     if (taskContext.isSchemaOnlyRecoverySnapshot()) {
                         startWithSnapshot = true;
 
@@ -95,6 +94,7 @@ public synchronized void start(Map<String, String> props) {
                         String msg = "The db history topic is missing. You may attempt to recover it by reconfiguring the connector to " + SnapshotMode.SCHEMA_ONLY_RECOVERY;
                         throw new ConnectException(msg);
                     }
+                    taskContext.initializeHistoryStorage();
                 } else {
 
                     // Before anything else, recover the database history to the specified binlog coordinates ...