This allows for more control over the mapping than with annotations.
We can for example specify an analyzer, and actually pass the value of index.

Jean-Baptiste Nizet authored Jul 26, 2018 and Exbrayat Cédric committed Jul 30, 2018

the examples lead to no result, and canis lupus is a wolf, so it doesn't belong to this database

fix: use test properties in application test to avoid touching/creating the production elastic search

 - initial requested page was 0, but the minimum is 1
 - new search kept the current page instead of resetting to default (1)
 - pagination was way too large to fit on any mobile
 - put it at the bottom, since this is not the most important part of the page

and also make the HTML simpler and cleaner (and prettier, IMHO)

Note that this feature revealed that the version of spring-data-elasticsearch that we're using was not compatible with the spring-data-commons version used by Spring Boot. So I upgraded the spring-data-commons version.

The time to harvest the 3 data files goes from 5 min. and 20 seconds. to 20 seconds, so it's a huge win, for a small additional complexity.

Also:
- configure actuator for more information
- use Import instead of SpringBootTest to add config classes to tests

also define the chema using annotations, although that doesn't seem to do exactly what we want

ng serve now proxies all /api and /actuator requests to the backend