Ryan Wynn

There could be another strategy added like you mention to specifically target index `a.b` if the document was deleted from colleciton `a.b`. But that does not exist yet. I think...

I don't believe a delete in MongoDB passes through the javascript function. Only if you update in MongoDB you can return `null` from the javascript middleware and it would attempt...

Hi @axpwx when you run with workers enabled you need to have 1 monstache process per worker. This is because workers means that, e.g. 3 processes will read from MongoDB...

This is a common question here and it is really an Elasticsearch thing. You may have different types in MongoDB for `created_at` field. That is why Elasticsearch is expecting a...

Hi @rpong just updated to the latest MongoDB driver version in the `rel6` and `rel5` branch. Please let me know what you find.

hi, can you please try with monstache v6 https://github.com/rwynn/monstache/releases/tag/v6.7.5 This version is compatible with recent versions of Elasticsearch

by default monstache sends the _id of the MongoDB document as the _id of the Elasticsearch document. Do you need something different?

Monstache just sends data to Elasticsearch. To control how that data is indexed you would need to configure on the Elasticsearch side. Take a look at [this](https://www.elastic.co/guide/en/elasticsearch/reference/current/dynamic-templates.html) and in [general](https://www.elastic.co/guide/en/elasticsearch/reference/current/mapping.html)

Thanks @swaddy I will look into that feature.

hi @oliveiracdz. there is not an option like this. My only thought would be to delete the index in the same cron job before kicking off the direct reads.