| > but then again org.hibernate.search.FullTextSession#createIndexer 'creates index' and populates them so I don't really need them to pre-exist Be careful, this method creates an Index*er* (in other words, an index populator), not an index. If the index does not exist, the mass indexing will fail.
When you use the NONE strategy, you have to create the indexes and mapping on Elasticsearch yourself. Hibernate Search will not do it, neither when starting up nor when mass indexing. In your case, the CREATE or MERGE strategies indeed seem to make more sense. Be careful about the MERGE strategy in a production environment, though (see the docs for a detailed explanation). > i suspect it may affect the application startup time.
It will, but then your application will not be fully started until you reindexed everything, which requires to create the indexes, so... > For me it is just confusing that IndexSchemaManagementStrategy.NONE actually checks for indexes existens...
I agree. PR coming. |
