Issues
- Validation failure messages should mention that they are related to Elasticsearch schema validationHSEARCH-3960Resolved issue: HSEARCH-3960Yoann Rodière
- Range predicate doesn't normalize arguments for text (analyzed) fields with ElasticsearchHSEARCH-3959
- Remove OSGi and Wildfly support and integration tests from legacy codeHSEARCH-3949Resolved issue: HSEARCH-3949Yoann Rodière
- Avoid creating huge arrays for collectors when a query does not have an upper bound limitHSEARCH-3947Resolved issue: HSEARCH-3947Fabio Massimo Ercoli
- ClassCastException: org.hibernate.search.backend.elasticsearch.types.sort.impl.ElasticsearchGeoPointFieldSortBuilderFactory cannot be cast to org.hibernate.search.backend.elasticsearch.types.sort.impl.ElasticsearchStandardFieldSortBuilderFactoryHSEARCH-3941Resolved issue: HSEARCH-3941Yoann Rodière
- HibernateOrmIntegrationBooterImpl confuses the startup event for a shutdown event, and vice-versaHSEARCH-3938Resolved issue: HSEARCH-3938Yoann Rodière
6 of 6
Currently the failures only mention the type, field, etc., but never mention that they are related to automatic schema validation, which is kind of confusing (e.g. here)
We should probably insert a context element below "type", something like this:
Alternatively, we could insert a failure message before anything else: