anchor.diff:  
   [[upgrade2.0.basic.requirements]]
   .Update to basic prerequisite minimums in HBase 2.0+
  -As noted in the section [[basic.prerequisites]], HBase 2.0+ requires a minimum of Java 8 and Hadoop 2.6. The HBase community recommends ensuring you have already completed any needed upgrades in prerequisites prior to upgrading your HBase version.
  +As noted in the section <<basic.prerequisites>>, HBase 2.0+ requires a minimum of Java 8 and Hadoop 2.6. The HBase community recommends ensuring you have already completed any needed upgrades in prerequisites prior to upgrading your HBase version.
   
   [[upgrade2.0.hbck]]
   .HBCK must match HBase server version
  
positive.code: 
  The following configuration settings are no longer applicable or available. For details, please see the detailed release notes.
  
  * hbase.config.read.zookeeper.config (see [[upgrade2.0.zkconfig]] for migration details)
  * hbase.zookeeper.useMulti (HBase now always uses ZK's multi functionality)
  * hbase.rpc.client.threads.max
  * hbase.rpc.client.nativetransport
  
negative.code: 
  HBase can no longer read the deprecated WAL files written in the Apache Hadoop Sequence File format. The hbase.regionserver.hlog.reader.impl and hbase.regionserver.hlog.reader.impl configuration entries should be set to use the Protobuf based WAL reader / writer classes. This implementation has been the default since HBase 0.96, so legacy WAL files should not be a concern for most downstream users.
  
  A clean cluster shutdown should ensure there are no WAL files. If you are unsure of a given WAL file's format you can use the `hbase wal` command to parse files while the HBase cluster is offline. In HBase 2.0+, this command will not be able to read a Sequence File based WAL. For more information on the tool see the section <<hlog_tool.prettyprint>>.
  
  [[upgrade2.0.filters]]
  .Change in behavior for filters
  