anchor.diff:      port: <number>         <13>
       dateFormat: "<format>" <14>
       longToString: <bool>   <15>
  -    auth:                   <16>
  +    clusterName: <string>  <16>
  +    auth:                  <17>
           user: <string>
           pwd: "password"
   ----
  
positive.code: = Mongolastic
  :version: v1.3.9
  
  image:https://travis-ci.org/ozlerhakan/mongolastic.svg?branch=master["Build Status", link="https://travis-ci.org/ozlerhakan/mongolastic"] image:https://img.shields.io/badge/license-MIT-blue.svg[] image:https://img.shields.io/badge/mongo.java.driver-3.2.2-brightgreen.svg[] image:https://img.shields.io/badge/elastic.java.driver-2.3.4-brightgreen.svg[]
  
  What data you have in your MongoDB can also be included into your ElasticSearch and vice versa using this tool. You can perform the aforementioned facilities by providing a file having a yaml characteristic.
  
  == How it works
  
  
negative.code: <13> the *transport* port where the transport module will communicate with the running elastic node. E.g. *9300* for node-to-node communication.
  <14> a custom formatter for Date fields rather than the default DateCodec (*Optional*)
  <15> serialize long value as a string for backwards compatibility with other tools (*Optional*)
  <16> the property lets you connect to a spesific elastic cluster (*Optional*)
  <17> as of v1.3.9, you can access an auth elastic search by giving auth configuration. (*Optional*)
  
  == Example
  
  Here is an example of a configuration file:
  
  