anchor.diff:  = Mongolastic
  -:version: v1.3.9
  +:version: v1.3.10
   
   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.
  +Mongolastic enables you to migrate your datasets from a mongod node to an elasticsearch node and vice versa. Since mongo and elastic servers can run with different characteristics, the tool provides several optional and required features to ably connect them. Mongolastic works with a yaml configuration file to begin a migration process. It reads your demand on the file and start syncing data in the specified direction.
   
   == How it works
   
  
positive.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> as of v1.3.9, you can access an auth elastic search by giving auth configuration. (*Optional*)
  
  Here is an example of a configuration file:
  
  
negative.code:     port: <number>         <13>
      dateFormat: "<format>" <14>
      longToString: <bool>   <15>
      clusterName: <string>  <16>
      auth:                  <17>
          user: <string>
          pwd: "password"
  ----
  