Tested by simply switching Reactive to Standard springData repository, the mappings do not match. The consequence is that most of the suggest, custom field configs, etc... won't work with Reactive repositories, on both index/mappings generation and querying/inserting operations
The reactive repository does not auto-create the index with the mapping. As autocreation is often problematic we probably should not add it to the repository class, but we need to add the necessary methods to the ReactiveElasticsearchOperations class.
As a workaround you can additionally define a non-reactive interface for your @Document class without using it, this will on startup create the index and mapping and then the index can be used with the reactive repository. But be aware hat this does on index creation blocking calls to the cluster
Yes, perfectly agree on both analysis and workaround (this is the workaround that I already had chosen). The blocking calls for the mappings is not a big issue as it is done at most once in a lifecycle