anchor.diff:  
   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.11.1/basic.html#register[REGISTER] command is used:
   
  +[source]
   ----
   REGISTER /path/elasticsearch-hadoop.jar;
   ----
  
positive.code: NOTE: the command expects a proper URI that can be found either on the local file-system or remotely. Typically it's best to use a distributed file-system (like HDFS or Amazon S3) and use that since the script might be executed
  on various machines.
  
  As an alternative, when using the command-line, one can register additional jars through the '-Dpig.additional.jars' option (that accepts an URI as well):
  
  ----
  pig -Dpig.additional.jars=/path/elasticsearch-hadoop.jar:<other.jars> script.pig
  ----
  
  or if the jars are on HDFS
  
  ----
  pig -Dpig.additional.jars=hdfs://<cluster-name>:<cluster-port>/<path>/elasticsearch-hadoop.jar:<other.jars> script.pig
  ----
  
  [[type-conversion-pig]]
  
negative.code: 
  As you would expect, loading the data is straight forward:
  
  [source]
  ----
  -- load data from Elasticsearch into Pig
  A = LOAD 'radio/artists/_search?q=me*'<1> USING org.elasticsearch.hadoop.pig.ESStorage(<2>);
  DUMP A;
  ----
  
  