anchor.diff:  {"ROWTIME":1529499994472,"ROWKEY":"null","id":2,"first_name":"Merilyn","last_name":"Doughartie","email":"mdoughartie1@dedecms.com","gender":"Female","club_status":"platinum","comments":"Optimized local definition"}
   ----
   
  -Press Ctrl-C to cancel and return to the KSQL prompt.
  +Press Ctrl-C to cancel and return to the KSQL prompt. This may take up to a minute to cancel (https://github.com/confluentinc/ksql/issues/1759[#1759]). If it still does not cancel then just start a new KSQL CLI using the `docker run` command from above and proceed to the next step. 
   
   <<<
   == KSQL offsets
   
   Since Apache Kafka persists data, it is possible to use KSQL to query and process data from the past, as well as new events that arrive on the topic.
   
  -To tell KSQL to process from beginning of topic run:
  -
  -`SET 'auto.offset.reset' = 'earliest';`
  +To tell KSQL to process from beginning of topic run `SET 'auto.offset.reset' = 'earliest';`
   
   Run this now, so that future processing includes all existing data—this is important for the Customer data, since no new messages are arriving on this topic and thus we need to make sure we work with the messages already present.
   
  
positive.code:           -t asgard.demo.CUSTOMERS
  ----
  
  You should see ten messages, similar to this:
  
  ----
  Key (-1 bytes):
  
negative.code: 
  [source,bash]
  ----
  # Make sure you run this from the `quickstart-demos/ksql-workshop` folder
  docker-compose exec -T kafka \
        kafka-console-consumer \
        --bootstrap-server kafka:29092 \
  