anchor.diff:  | `double`          | `double`
   | `float`           | `float`
   | `bytearray`       | `binary`
  -| `tuple`           | `map`
  +| `tuple`           | `array` or `map` (depending on <<tuple-names,this>> settings)
   | `bag`             | `array`
   | `map`             | `map`
   
  
positive.code: DEFINE EsStorage org.elasticsearch.hadoop.pig.EsStorage('my.cfg.param=value');
  ----
  
  IMPORTANT: Pig definitions are replaced as are; even though the syntax allows _parametrization_, Pig will silently ignore any parameters outside the 'DEFINE' declaration.
  
  [[pig-alias]]
  [float]
  
negative.code: ____
  http://pig.apache.org/[Apache Pig] is a platform for analyzing large data sets that consists of a high-level language for expressing data analysis programs, coupled with infrastructure for evaluating these programs.
  ____
  It provides a high-level, powerful, _scripting_-like transformation language which gets compiled into {mr} jobs at runtime by the Pig 'compiler'. To simplify working with arbitrary data, Pig associates a 'schema' (or type information) with each data set for validation and performance. This in turn, breaks it down into 'discrete' data types that can be transformed through various operators or custom functions (or http://pig.apache.org/docs/r0.12.1/udf.html[UDF]s). Data can be loaded from and stored to various storages such as the local file-system or HDFS, and with {eh} into {es} as well.
  
  [[pig-installation]]
  [float]
  === Installation
  
  In order to use {eh}, its jar needs to be in Pig's classpath. There are various ways of making that happen though typically the http://pig.apache.org/docs/r0.12.1/basic.html#register[REGISTER] command is used:
  
  [source,sql]
  ----
  