Hi Zoltan,
This is a reasonable thing to want to do. The database change protocol used by the connector places some limitations on us though. Deletion notifications do not include the content of the deleted document. This means the connector would not be able to route deletions to the correct index. In the past we’ve accommodated this by adding an “ignoreDeletes” flag to the the definition, and requiring it be set to true for all rules that need to inspect the document content.
Does your use case require that deletions propagate to Elasticsearch, or would you be happy with setting ignoreDeletes=true for types whose ES index is determined by content fields?
Thanks,
David