This is typically what happens when you use an indexing management strategy that does not generate nor check the schema, such as create or none. Hibernate Search sent to Elasticsearch something that didn't fit the schema, and Elasticsearch automatically guessed what the schema should be. Like often, it guessed wrong: it's really hard to know the schema from just a value. Why I'm sure of that:
- Hibernate Search does not create "fields" in Elasticsearch properties, except in very specific cases (faceting)
- We really didn't change much in the Elasticsearch backend between 5.10 and 5.11, and nothing related to multi-tenancy IIRC.
The solution in your case would be to drop the indexes, start Hibernate Search with a strategy that creates the indexes and their schema (create should be safe), and only then reindex. I will close this ticket because it's not a bug, or at least not the one described here, but feel free to open a question on stackoverflow (tag hibernate-search) or on our Discourse instance: I'll be glad to help. |