anchor.diff:  }
   ----
   
  -The emitted event has a slightly different set of values that the legacy oplog output.
  +The emitted event has a slightly different set of values than the legacy oplog output.
   As shown above, the event does not have a value in the after, patch, or filter fields.
   Instead, the event relies on describing the changes to the document's fields in the `updateDescription` structure.
   While this provides a bit more detail about values that may have been set and even unset due to an update,
  
positive.code: 
  In conjunction to the work already done with MongoDB change streams, we recognize there is much work that remains which includes testing the new change streams implementations against MongoDB 5 and updating the connector documentation to reflect these new changes.
  You can expect this and much more as a part of the next preview release.
  
  == Other Fixes
  
  There were quite a number of bugfixes and stability changes in this release, some noteworthy are:
  
  * Row hashing in LogMiner Query not able to differentiate between rows of a statement. https://issues.redhat.com/browse/DBZ-3834[DBZ-3834]
  * The chunk select statement is incorrect for combined primary key in incremental snapshot https://issues.redhat.com/browse/DBZ-3860[DBZ-3860]
  * column.the mask.hash.hashAlgorithm.with.... data corruption occurs when using this feature https://issues.redhat.com/browse/DBZ-4033[DBZ-4033]
  * Infinispan SPI throws NPE with more than one connector configured to the same Oracle database https://issues.redhat.com/browse/DBZ-4064[DBZ-4064]
  
  Altogether, https://issues.redhat.com/issues/?jql=project%20%3D%20DBZ%20AND%20fixVersion%20%3D%201.8.0.Alpha1%20ORDER%20BY%20component%20ASC[82 issues] were fixed for this release.
  A big thank you to all the contributors from the community who worked on this release:
  
negative.code: Specifies that changes should  be captured by tailing the oplog; this is the legacy behavior.
  `change_streams`::
  Specifies that changes should be captured by using MongoDB change streams.
  Updates will not contain the full message; only changed fields are part of the event.
  `change_streams_update_full`::
  Specifies that changes should be captured by using MongoDB change streams.
  Updates will contain a full snapshot of the current record in the event.
  