anchor.diff:      mysql> INSERT INTO customers VALUES (default, "Kenneth", "Anderson", "kander@acme.com");
   ----
   
  -Notice that in the terminal where we're running `watch-topic`, there's been no update. Also, we're still able to watch the topic because Kafka is still running. 
  +Notice that in the terminal where we're running `watch-topic`, there's been no update. Also, we're still able to watch the topic because Kafka is still running.
   
   [TIP]
   ====
  
positive.code: ...
  ----
  
  Each of these steps reports what the connector is doing to perform the consistent snapshot. For example, Step 6 involves reverse engineering the DDL create statements for the tables that are being captured; Step 7 releases the global write lock just 0.3 seconds after acquiring it, and Step 8 reads all of the rows in each of the tables and reports the time taken and number of rows found. Note that in our example database, the MySQL connector completed its consistent snapshot in just 0.38 seconds. 
  
  [NOTE]
  ====
  
negative.code: }
  ----
  
  This response describes the connector resource `/connectors/inventory-connector` that the service just created and includes the connector's configuration and information about the tasks. Since the connector was just created, the service hasn't yet finished starting tasks.
  
  We can even use the RESTful API to verify that our connector is included in the list of connectors:
  
  