anchor.diff:  
   UPDATE STATISTICS processing time can be lengthy for very large tables.
   One strategy for reducing the time is to create histograms only for
  -columns that actually need them (for example, using the ON NECESSARY COLUMNS 
  +columns that actually need them (for example, using the ON NECESSARY COLUMNS
   column group). Another strategy is to update statistics incrementally. These
   strategies can be used together if desired.
   
  
positive.code: {project-name}:
  
  * Reads Hive metadata to determine information about table.
  * UPDATE STATISTICS can be performed on Hive tables - improves performance! 
  * Can write to Hive tables in both Text and Sequence formats (used by UNLOAD).
  
  <<<
  [[load_examples]]
  === Examples of LOAD
      
  * For customer demographics data residing in
  `/hive/tpcds/customer_demographics`, create an external Hive table using
  the following Hive SQL:
  
negative.code: columns, skew in data, etc. LOAD sas upsert semantics (duplicate constraint
  not checked with existing data). LOAD has lower CPU abd disk activity than
  similar trickle load (INSERT, UPSERT, or UPSERT USING LOAD), Also, LOAD has
  lower compaction activity after completion than Trickle Load.
  
  ==== Hive Scans
  
  