anchor.diff:  DEFINE ESStorage org.elasticsearch.hadoop.pig.ESStorage('es.resource=radio/artists/');"
   ----
   
  -Do note that it is possible (and recommended) to specify the configuration parameters to reduce script duplication.
  +Do note that it is possible (and recommended) to specify the configuration parameters to reduce script duplication. In fact, for the reminder of this section, 
  +the Pig alias will be implied and +ESStorage+ will be used (instead of the fully qualified class name) for abbreviation.
   
   [[pig-alias]]
   === Mapping
   
   Out of the box, {eh} uses the Pig 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 Pig cannot
  -be used with {es} (invalid characters, existing names with different layout, etc...). For such cases, one can use the +es.column.aliases+ setting which accepts a comma-separated list of names mapping in the following format: ++Pig field name+ : ++{es field name}++
  +be used with {es} (invalid characters, existing names with different layout, etc...). For such cases, one can use the +es.column.aliases+ setting which accepts a comma-separated list of names mapping in the following format: ++Pig field name+ : ++{es} field name++
   
   For example:
   
  
positive.code: -- transform data
  B = FOREACH A GENERATE name, TOTUPLE(url, picture) AS links;
  -- save the result to Elasticsearch
  STORE B INTO 'radio/artists'<1> USING org.elasticsearch.hadoop.pig.ESStorage(<2>);
  ----
  
  <1> {es} resource (index and type) associated with the given storage
  
negative.code: [source]
  ----
  -- load data from Elasticsearch into Pig
  A = LOAD 'radio/artists/_search?q=me*'<1> USING ESStorage(<2>);
  DUMP A;
  ----
  
  