Hi - Currently, when using external versioning, ElasticSearch always returns the same error when there is a version number conflict, eg: VersionConflictEngineException[[twitter][2] [tweet][1]: version conflict, current [3], required [2]] Is it possible to change this so that a different error is…

Topic		Replies	Views
Version Conflicts Elasticsearch	2	305	July 6, 2017
External version does not behave per documentation Elasticsearch	4	366	July 6, 2017
Just Pushed: Versioning Elasticsearch	13	1330	July 6, 2017
Getting Exception with Versioning? Elasticsearch	1	519	July 6, 2017
ElasticSearch document versioning Elasticsearch	6	833	July 6, 2017

Elasticsearch is a trademark of Elasticsearch BV, registered in the U.S. and in other countries
Trademarks
Terms
Privacy
Brand
Code of Conduct

Apache, Apache Lucene, Apache Hadoop, Hadoop, HDFS and the yellow elephant logo are trademarks of the Apache Software Foundation in the United States and/or other countries.

Idempotent indexing into ElasticSearch when neither data nor version number have changed?

Related topics