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: FlowConnector flow = new HadoopFlowConnector(props);
  ----
  
  {eh} options can be specified in the same way, these being picked up automatically by all `EsTap`s down the flow:
  
  [source,java]
  ----
  
negative.code: This approach can be used for local and remote/Hadoop flows - simply use the appropriate `FlowConnector`.
  
  [float]
  ==== Per-`Tap` configuration
  If a `flow` contains multiple `{es}` taps, the global approach does not work since the settings will clash with each other.  For these scenario, `{eh}` allows using per-`Tap` configuration:
  
  [source,java]
  ----
  Tap books = new EsTap("es-server", 9200, "my-col/books", "?q=potter");
  Tap movies = new EsTap("es-server", 9200, "my-col/movies", "?q=terminator");
  ----
  
  Note that the `Tap` configuration is merged with the global one so one can mix and match accordingly - for example specify the defaults in the global configuration and only declare the specifics on the `Tap` instance. Additionally, for maximum flexibility `EsTap` allows multiple arguments to be passed in, including a `Properties` object for the full range of options.
  
  
  [[cascading-writing]]
  [float]
  