Add failed then all update failed as well about elasticstore

[acupofjose]

Yep! That would do it.

There are some tutorials out there on how to update/change mappings in Elasticsearch.

If your app is still in heavy development, my approach would be to blow out the existing index, insert a fully defined document, and reinsert everything into elasticsearch. But that's just me.

Here's a blog entry on changing the mapping:
https://www.elastic.co/blog/changing-mapping-with-zero-downtime

As this isn't a problem with the library in particular, I'll close this issue. If you end up having other problems with it, please let me know!

[acupofjose]

@alaindixon, thanks for using the library! Is your firestore document VDPUYRBpKg3sJO4nwMgd conforming to the same types as the other documents in your collection?

Elasticsearch defines the mapping of an index based off the document it first receives (or the mapping you specify in the configuration). If it receives a document that does not conform to the existing type mapping, it will reject it. (i.e. trying to insert an Object where a float should be)

You can see a similar thread here: elastic/elasticsearch-py#579

[alaindixon]

Thank you for your very quick response, awesome.
Basically I could order several products, I've got a field "menuDetail", I think it was null in the first place.
What would you recommand?