Currently the reactive code relies on the Elasticsearch index to be available. In contrast to the non-reactive parts it is not possible to create an index and put the document's mapping in the ReactiveElasticsearchOperations implementations.
Operations like createIndex() and putMapping() need to be defined in ReactiveIndexOperations interface and implemented in the corresponding implementation class(es).
The functionality should be the same that is available in the non-reactive IndexOperations interface
Affects: 4.0 M1 (Neumann)
Issue Links:
DATAES-655 Reactive repository ignores entity class annotations
what's not yet implemented but is available in the non-reactive part are the alias-management functions. But these will be rewritten anyway in DATAES-864
sothawo opened DATAES-678 and commented
Currently the reactive code relies on the Elasticsearch index to be available. In contrast to the non-reactive parts it is not possible to create an index and put the document's mapping in the
ReactiveElasticsearchOperations
implementations.Operations like
createIndex()
andputMapping()
need to be defined inReactiveIndexOperations
interface and implemented in the corresponding implementation class(es).The functionality should be the same that is available in the non-reactive
IndexOperations
interfaceAffects: 4.0 M1 (Neumann)
Issue Links:
Referenced from: pull request #481
The text was updated successfully, but these errors were encountered: