anchor.diff:  
   === Columns
   
  -* CHAR, VARCHAR, DATE, and complex types like ARRAY are not supported.
  +* 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.
  +* Tables can have a maximum of 300 columns by default.
   
   === Tables
   
  
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: 
  == Scale
  
  Kudu is known to run seamlessly across a wide array of environments and workloads
  with minimal expertise and configuration at the following scale:
  
  * 3 master servers
  
  * 100 tablet servers
  
  * 8 TiB of stored data per tablet server, post-replication and post-compression.
  
  * 1000 tablets per tablet server, post-replication.
  
  * 60 tablets per table, per tablet server, at table-creation time.
  
  * 10 GiB of stored data per tablet.
  
  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
  
  * 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
  