anchor.diff:  
   <1> {eh} resource (index and type)
   <2> {eh} query
  +
  +
  +[float]
  +=== Type conversion
  +
  +Depending on the http://docs.cascading.org/cascading/2.1/userguide/htmlch03s04.html[platform] used, Cascading can use internally either `Writable` or JDK types for its tuples. {es} handles both transparently 
  +(see the {mr} <<type-conversion-writable,conversion>> section) though we recommend using the same types (if possible) in both cases to avoid the overhead of maintaining two different versions.
  +
  +IMPORTANT: If automatic index creation is used, please review <<auto-mapping-type-loss,this>> section for more information.
  
positive.code: This approach can be used for local and remote/Hadoop flows - simply use the appropriate `FlowConnector`.
  
  [float]
  === Type conversion
  
  Depending on the http://docs.cascading.org/cascading/2.1/userguide/htmlch03s04.html[platform] used, Cascading can use internally either `Writable` or JDK types for its tuples. {es} handles both transparently 
  (see the {mr} <<type-conversion-writable,conversion>> section) though we recommend using the same types (if possible) in both cases to avoid the overhead of maintaining two different versions.
  
  IMPORTANT: If automatic index creation is used, please review <<auto-mapping-type-loss,this>> section for more information.
  
  [[cascading-writing]]
  [float]
  
negative.code: <1> Indicate the input is of type JSON.
  <2> Load the (JSON) data as a single field (`line`)
  
  
  [float]
  ==== Writing to dynamic/multi-resources
  
  One can index the data to a different resource, depending on the tuple being read by using patterns. Reusing the aforementioned <<cfg-multi-writes,media example>>, one could configure it as follows:
  
  [source,java]
  ----
  Tap out = new EsTap("es.resource.write", "my-collection/{media.type}");
  ----
  
  For each tuple about to be written, {eh} will extract the `media.type` entry and use its value to determine the target resource. The functionality is available when dealing with raw JSON as well - the value will be extracted from the document itself.
  
  [float]
  === Reading data from {es}
  
  