anchor.diff:  = Mongolastic
   :version: v1.4.0
   
  -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.4.0-brightgreen.svg[] image:https://img.shields.io/badge/elastic.java.driver-5.1.1-brightgreen.svg[]
  +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.4.1-brightgreen.svg[] image:https://img.shields.io/badge/elastic.java.driver-5.1.1-brightgreen.svg[]
   
   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 or json configuration file to begin a migration process. It reads your demand on the file and start syncing data in the specified direction.
   
  
positive.code: 
  the config says that the transfer direction is from mongodb to elasticsearch, mongolastic first looks at the _tweets_ collection, where the _user name_ is _kodcu.com_, of the _twitter_ database located on a mongod server running on default host interface and port number. If It finds the corresponding data, It will start copying those into an elasticsearch environment running on default host and transport number. After all, you should see a type called _"posts"_ in an index called _"kodcu"_ in the current elastic node. Why the index and type are different is because "dindex.as" and "ctype.as" options were set, these indicates that your data being transferred exist in _posts_ type of the _kodcu_ index.
  
  After downloading the jar and providing a conf file, you can either run the tool as:
  
      $ java -jar mongolastic.jar -f config.file
  
  __or__
  
      $docker run --rm -v $(PWD)/config.file:/config.file --net host ozlerhakan/mongolastic:<tag> config.file
  
  NOTE: Every attempt of running the tool drops the mentioned db/index in the target environment unless the dropDataset parameter is configured otherwise.
  
  
negative.code: 
  Supported tags and respective Dockerfile links:
  
  *  `_1.4_`, `_1.4.0_`, `_latest_` https://github.com/ozlerhakan/mongolastic/blob/master/Dockerfile[_(master/Dockerfile)_]
  *  `_1.3_`, `_1.3.15_` https://github.com/ozlerhakan/mongolastic/blob/8e7494852ad601b58be25224e141f1cfed507d9c/Dockerfile[_(1.3.15/Dockerfile)_]
  
  
  or download the latest https://github.com/ozlerhakan/mongolastic/releases/download/{version}/mongolastic.jar[mongolastic.jar] file.
  