anchor.diff:  Below is an example for a configuration which replaces a part of the table in the topic with another string, allowing two tables to emit changes to the same topic:
   
   [source]
  ----
  +----
   transforms=Reroute
   transforms.Reroute.type=io.debezium.transforms.ByLogicalTableRouter
   transforms.Reroute.topic.regex=(.*)customers_shard(.*)
   transforms.Reroute.topic.replacement=$1customers_all_shards
  ----
  +----
   
   The configuration above will match topics such as `myserver.mydb.customers_shard1`, `myserver.mydb.customers_shard2` etc. and replace it with `myserver.mydb.customers_all_shards.`
   
  
positive.code: For example the following configuration will use the name `shard_id` for the key field:
  
  [source]
  ---
  ...
  transforms.Reroute.key.field.name=shard_id
  ...
  ---
  
  The _value_ of the field can be adjusted via the `key.field.regex` and `key.field.replacement` properties.
  The former allows you to define a regular expression that will be applied to the original topic name to capture one or more groups of characters.
  
negative.code: For example:
  
  [source]
  ----
  ...
  transforms.Reroute.key.field.regex=(.*)customers_shard(.*)
  transforms.Reroute.key.field.replacement=$2
  ----
  
  This will apply the given regular expression to original topic names and use the second capturing group as value for the key field.
  Assuming the source topics are named `myserver.mydb.customers_shard1`, `myserver.mydb.customers_shard2` etc., the key field's values would be `1`, `2` etc.
  