anchor.diff:  ----
   
   .Javascript with Graal.js
  -When you create filtering conditions by using JavaScript with Graal.js, you use an approach that is similar to the one use with Groovy.
  +When you create filtering conditions by using JavaScript with Graal.js, you use an approach that is similar to the one that you use with Groovy.
   For example:
   
   [source,javascript]
  
positive.code: |`value` |A value of the message. |`org.apache.kafka.connect.data.Struct`
  |`keySchema` |Schema of the message key.|`org.apache.kafka.connect.data.Schema`
  |`valueSchema`|Schema of the message value.| `org.apache.kafka.connect.data.Schema`
  |`topic`|Name of the target topic.| N/A
  |`headers`|The map of message headers keyed with header name and value composed of `schema` and `value` variables| N/A
  |=======================
  
  An expression can invoke arbitrary methods on its variables. 
  The expression should resolve to a Boolean value that determines whether the message is removed (`true`) or kept.
  Expressions should not result in any side-effects. That is, they should not modify any variables that they pass.
  
  // Type: reference
  
negative.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.
  
  