anchor.diff:  CREATE EXTERNAL TABLE artists (...)
   STORED BY 'org.elasticsearch.hadoop.hive.ESStorageHandler'
   TBLPROPERTIES('es.resource' = 'radio/artists/',
  -            <1>'es.column.aliases' = 'date:@timestamp<2>, url:url_123<3>');
  +            <1>'es.column.aliases' = 'date:@timestamp <2>, url:url_123 <3>');
   ----
   
   <1> name mapping for two fields
  
positive.code: | `array`           | `array`
  | `union`           | not supported yet
  
  2`h| Available in Hive 0.11 or higher
  
  | `decimal`         | `string`
  
  
negative.code: === Mapping
  
  By default, {eh} uses the Hive table schema to map the data in {es}, using both the field names and types in the process. There are cases however when the names in Hive cannot
  be used with {es} (the field name can contain characters accepted by {es} but not by Hive). For such cases, one can use the `es.column.aliases` setting which accepts a comma-separated list of names mapping in the following format: `Hive field name`:`{es} field name`
  
  To wit:
  
  