When using versioning, there is currently no way to force a document to be indexed when the same or newer version already exists. This would be useful when, for instance, ElasticSearch contains data replicated from RDMS, and there has been a transaction rollback.
One option would be a mode in which ElasticSearch does index the older document, but still returns the VersionConflictEngineException as a warning to the user.
When using versioning, there is currently no way to force a document to be indexed when the same or newer version already exists. This would be useful when, for instance, ElasticSearch contains data replicated from RDMS, and there has been a transaction rollback.
One option would be a mode in which ElasticSearch does index the older document, but still returns the VersionConflictEngineException as a warning to the user.
See also https://github.com/elasticsearch/elasticsearch/issues/2166