anchor.diff:  
   == Scale
   
  -* Recommended maximum number of tablet servers is 100.
  +Kudu is known to run seamlessly across a wide array of environments and workloads
  +with minimal expertise and configuration at the following scale:
   
  -* Recommended maximum number of masters is 3.
  +* 3 master servers
   
  -* Recommended maximum amount of stored data, post-replication and post-compression,
  -  per tablet server is 8 TiB.
  +* 100 tablet servers
   
  -* The maximum number of tablets per tablet server is 2000, post-replication,
  -  but we recommend 1000 tablets or fewer per tablet server.
  +* 8 TiB of stored data per tablet server, post-replication and post-compression.
   
  -* Maximum number of tablets per table for each tablet server is 60,
  -  post-replication (assuming the default replication factor of 3), at table-creation time.
  +* 1000 tablets per tablet server, post-replication.
   
  -* Recommended maximum amount of data per tablet is 50 GiB. Going beyond this can cause
  -  issues such a reduced performance, compaction issues, and slow tablet startup times.
  -  The recommended target size for tablets is under 10 GiB.
  +* 60 tablets per table, per tablet server, at table-creation time.
   
  -== Replication and Backup Limitations
  +* 10 GiB of stored data per tablet.
   
  -* Kudu does not currently include any built-in features for backup and restore.
  -  Users are encouraged to use tools such as Spark or Impala to export or import
  -  tables as necessary.
  +Staying within these limits will provide the most predictable and straightforward
  +Kudu experience.
  +
  +However, experienced users who run on modern hardware, use the latest
  +versions of Kudu, test and tune Kudu for their use case, and work closely with
  +the community, can achieve much higher scales comfortably. Below are some
  +anecdotal values that have been seen in real world production clusters:
  +
  +* 3 master servers
  +
  +* 300+ tablet servers
  +
  +* 10+ TiB of stored data per tablet server, post-replication and post-compression.
  +
  +* 4000+ tablets per tablet server, post-replication.
  +
  +* 50 GiB of stored data per tablet. Going beyond this can cause issues such a
  +  reduced performance, compaction issues, and slow tablet startup times.
   
   == Security Limitations
   
  -* Authorization is only available at a system-wide, coarse-grained level. Table-level,
  -  column-level, and row-level authorization features are not available.
  +* Row-level authorization is not available.
   
   * Data encryption at rest is not directly built into Kudu. Encryption of
     Kudu data at rest can be achieved through the use of local block device
  
positive.code: 
  * Server certificates generated by Kudu IPKI are incompatible with
    link:https://www.bouncycastle.org/[bouncycastle] version 1.52 and earlier. See
    link:https://issues.apache.org/jira/browse/KUDU-2145[KUDU-2145] for details.
  
  == Other Known Issues
  
  
negative.code: 
  === Columns
  
  * CHAR, VARCHAR, DATE, and complex types like ARRAY, MAP, and STRUCT are not supported.
  
  * Type and nullability of existing columns cannot be changed by altering the table.
  
  * The precision and scale of `DECIMAL` columns cannot be changed by altering the table.
  
  * Tables can have a maximum of 300 columns by default.
  
  === Tables
  
  