anchor.diff:  
   The way that you express filtering conditions depends on the scripting language that you use.
   
  -For example, as shown in {link-prefix}:{link-filtering}#example-of-configuring-filter-conditions[], when you use `Groovy` as the expression language, 
  +For example, as shown in {link-prefix}:{link-filtering}#example-basic-debezium-filter-smt-configuration[], when you use `Groovy` as the expression language, 
   the following expression removes all messages, except for update records that have `id` values set to `2`:
   
   [source,groovy]
  
positive.code: 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).
  
  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.
  
  The filter SMT supports scripting languages that integrate with https://jcp.org/en/jsr/detail?id=223[JSR 223] (Scripting for the Java(TM) Platform).
  
  Kafka Connect provides its own link:https://cwiki.apache.org/confluence/display/KAFKA/KIP-66%3A+Single+Message+Transforms+for+Kafka+Connect[Simple Message Transforms] (SMT) to encode filtering logic.
  
negative.code: // ModuleID: variables-for-use-in-filter-expressions
  == Variables for use in filter expressions
  
  {prodname} binds certain variables into the evaluation context for the filter SMT.
  When you create expressions to specify filter conditions, you can use the variables that {prodname} binds into the evaluation context.
  By binding variables, {prodname} enables the SMT to look up and interpret their values as it evaluates the conditions in an expression. 
  
  The following table lists the variables that {prodname} binds into the evaluation context for the filter SMT:
  
  