anchor.diff:  
       $ java -jar target/mongolastic.jar query.mongolastic fileName:tweets
   
  -This command will simply give a new name called "tweets" to the JSON bulk file rather than "tweetsJSON".
  +This command will simply give a new name called "tweets" to the JSON bulk file rather than "output".
   
   == Extra Info
   
  
positive.code: .the query anatomy
  [source,xml]
  ----
  [transfer|export|copy] [database-name]/[collection-name]
  from <declarations>
  to file = { name: [file-name] }
  [and  <declarations>]?
  
  <declarations> := mongo = <config>
                  | es    = <config>
  
  <config> := { host: host-machine , port: port-number }
  ----
  
  NOTE: Mongolastic supports 'from mongo to file and *optionally* es' direction for now. You can either use upper-case or lower-case for the keywords (e.g. FROM, PORT, AND, etc.)
  
  Here is an example of a mongolastic query:
  
  
negative.code: [width="100%",options="header"]
  |====================
  | Property | Description
  | _mongoHost_ |  Specifies the name of the host machine where the `mongod` is running.
  | _mongoPort |  Specifies the port where the `mongod` instance is listening.
  | _db_ or _database_ |  Specifies the _database name_ to connect to.
  | _c_ or _collection_  |  Specifies the _collection name_ to export.
  | _fileName_ |  Specifies the _name_ of the new JSON file.
  | _esHost_ |  Specifies the name of the host machine where the `elastic node` is running.
  | _esPort_ | Specifies the *transport* port where the transport module will communicate with the running elastic node. E.g. *9300* for node-to-node communication.
  |====================
  
  IMPORTANT: You can pass parameters up to _7 config key:value pairs_ + _a mongolastic query file_ to Mongolastic. If you pass unknown parameters not being a key:value pair, Mongolastic will discard them and consider the properties of a given query file.
  