anchor.diff:  
   +++<!-- more -->+++
   
  -== MongoDB Change Stream Support
  +== MongoDB Change Streams Support
   
   MonogoDB https://docs.mongodb.com/manual/changeStreams/[change streams] allow an application or client access to real-time change data capture events without the complexity of tailing the oplog.
   This functionality was first introduced by the MongoDB engine in version 3.6; however the functionality was limited.
   Starting with MongoDB 4.0, change streams now captures changes across a database, replica set, or even a sharded cluster.
   
  -Debezium added change stream support to:
  +Debezium added change streams support to:
   
   * Enable compatibility with MongoDB 5 (not yet tested, see future work below).
  -* Possibly become a replacement for oplog reading.
   * Provide full document output in update events (see below).
  +* Abstract from internal (and potentially changing) specifics of the oplog format, making this new implementation a potential replacement for oplog reading in the future.
   
   In order to use change stream support with Debezium, you must use MongoDB 4.0 or later.
   
  
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: }
  ----
  
  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,
  