anchor.diff:  However, in many cases, you might be interested in only a subset of the events emitted by the producer. 
   To enable you to process only the records that are relevant to you, {prodname} provides the _filter_ simple message transform (SMT).
   
  -Configure this transformation in the {prodname} connector's Kafka Connect configuration.
  -By configuring the filter SMT, you can specify the events that you are interested in by defining filter conditions based on business rules.
  +You configure the filter transformation in the {prodname} connector's Kafka Connect configuration.
  +In the configuration, you specify the events that you are interested in by defining filter conditions that are based on business rules.
   As the filter SMT processes the event stream, it evaluates each event against the configured filter conditions.
   Only events that meet the criteria of the filter conditions are passed to the broker.
   
  
positive.code: 
  |[[filter-null-handling-mode]]<<filter-null-handling-mode, `null.handling.mode`>>
  |`keep`
  |Prescribes how the transformation handles `null` (tombstone) messages. The options are: `keep` (the default) to pass the message through, `drop` to remove the messages completely or `evaluate` to run the message through the condition expression.
  
  |===
  
negative.code: ----
  
  The preceding example specifies the use of the `Groovy` expression language.
  The regular expression `value.op == 'u' && value.before.id == 2` removes all messages, except those that represent update (`u`) records with `id` values that are equal to `2`.
  
  [IMPORTANT]
  ====
  