Elasticsearch 6: Rejecting mapping update as the final mapping would have more than 1 type

Question

I\'m trying to convert a project to use the latest Elasticsearch 6 and am having this problem. I don\'t know if the problem is \"Product\" vs \"product\". In my mappings and att

Answer 1

As Batsu says, from version 5 of elasticSearch onwards, the concept of treating the index as the database and the type as a table was removed to implement a lucene optimization.

The solution is to use an index by @Document.

Referral: https://www.elastic.co/guide/en/elasticsearch/reference/6.7/removal-of-types.html