anchor.diff:                    (defaults to true)
    doPuts           if false, does not perform puts
                     (defaults to true)
  + ignoreTimestamps if true, ignores cells timestamps while comparing
  +                  cell values. Any missing cell on target then gets
  +                  added with current time as timestamp
  +                  (defaults to false)
   
   Args:
    sourcehashdir    path to HashTable output dir for source table
  
positive.code: all released versions.
  For major 1.x versions, minimum minor release including it is *1.4.10*.
  For major 2.x versions, minimum minor release including it is *2.1.5*.
  ====
  
  .Set doDeletes to false on Two-Way Replication scenarios
  
negative.code:  $ bin/hbase org.apache.hadoop.hbase.mapreduce.SyncTable --dryrun=true --sourcezkcluster=zk1.example.com,zk2.example.com,zk3.example.com:2181:/hbase hdfs://nn:9000/hashes/tableA tableA tableA
  ----
  
  Cell comparison takes ROW/FAMILY/QUALIFIER/TIMESTAMP/VALUE into account for equality. When syncing at the target, missing cells will be
  added with original timestamp value from source. That may cause unexpected results after SyncTable completes, for example, if missing
  cells on target have a delete marker with a timestamp T2 (say, a bulk delete performed by mistake), but source cells timestamps have an
  older value T1, then those cells would still be unavailable at target because of the newer delete marker timestamp. Since cell timestamps
  might not be relevant to all use cases, _ignoreTimestamps_ option adds the flexibility to avoid using cells timestamp in the comparison.
  When using _ignoreTimestamps_ set to true, this option must be specified for both HashTable and SyncTable steps.
  
  The *dryrun* option is useful when a read only, diff report is wanted, as it will produce only COUNTERS indicating the differences, but will not perform
  any actual changes. It can be used as an alternative to VerifyReplication tool.
  
  