Requirements:
* drop annotation-based definitions, and rely exclusively on analysis definition providers (such as org.hibernate.search.elasticsearch.analyzer.definition.ElasticsearchAnalysisDefinitionProvider in Search 5)
* drop support for assigning an analyzer to an entity or to a property (we used to allow it in Search 5). We'll have to keep it in the compatibility layer, though (HSEARCH-3282)
* users will configure their own analyzer definition through a backend-scoped configuration property
* we may want to offer a set of built-in definitions for Lucene, to make it easier to build a simple (simplistic?) application. We should make sure to be as consistent as possible with Elasticsearch and Solr when naming the analyzers. => Moved to HSEARCH-2584
* make analyzer/normalizer definitions fully backend-specific (the engine shouldn't have to care)
* for Lucene, still only scope analyzer definitions globally (never per index)
* for Elasticsearch, we will (later) offer the ability the scope analyzer definitions either globally or by type; see HSEARCH-3309
|
|
