anchor.diff:  
   |[[vitess-property-tasks-max]]<<vitess-property-tasks-max, `+tasks.max+`>>
   |`1`
  -|The maximum number of tasks that should be created for this connector. The Vitess connector always uses a single task and therefore does not use this value, so the default is always acceptable.
  +|The maximum number of tasks that should be created for this connector. The Vitess connector can use more than 1 tasks if you enable offset.storage.per.task mode.
   
   |[[vitess-property-database-hostname]]<<vitess-property-database-hostname, `+database.hostname+`>>
   |
  
positive.code: 
  You can send this configuration with a `POST` command to a running Kafka Connect service. The service records the configuration and starts the connector task that connects to the Vitess database and streams change event records to Kafka topics.
  
  // Type: procedure
  // ModuleID: adding-debezium-vitess-connector-configuration-to-kafka-connect
  // Title: Adding {prodname} Vitess connector configuration to Kafka Connect
  
negative.code: `false` - only a _delete_ event is emitted. +
   +
  After a source record is deleted, emitting a tombstone event (the default behavior) allows Kafka to completely delete all events that pertain to the key of the deleted row in case {link-kafka-docs}/#compaction[log compaction] is enabled for the topic.
  
  |[[vitess-property-offset-storage-per-task]]<<vitess-property-offset-storage-per-task, `+vitess.offset.storage.per.task+`>>
  |`false`
  |Specify whether to turn on offset-storage-per-task mode launch multiple connector tasks and persist offsets partitioned by task. +
   +
  `true` - turn on offset-storage-per-task mode.  +
   +
  `false` - do not use offset-storage-per-task mode. +
   +
  You will also you also need to specify vitess.offset.storage.task.key.gen and vitess.prev.num.tasks params if you turn on offset-storage-per-task mode.
  
  |[[vitess-property-offset-storage-task-key-gen]]<<vitess-property-offset-storage-task-key-gen, `+vitess.offset.storage.task.key.gen+`>>
  |`-1`
  |Specify the task paralleism generation number when vitess.offset.storage.per.task is turned on. You should increase the generation number when you decide to change the connector task parallelism (either launch more connector tasks or less)
  
  |[[vitess-property-prev-num-tasks]]<<vitess-property-prev-num-tasks, `+vitess.prev.num.tasks+`>>
  |`-1`
  |Specify the number of connector tasks used in the previous generation of task paralleism when vitess.offset.storage.per.task is turned on.
  
  |[[vitess-property-message-key-columns]]<<vitess-property-message-key-columns, `+message.key.columns+`>>
  |_empty string_
  