MantainDs function is coupling with Elastic Search engine?

[latta-siae]

As far I have understood the generic word DataStore we are now referencing as Elastic Search.
Is this the default engine or we have to refer/take in account also others datastore engines?

https://github.com/openBackhaul/DevicePerformanceManagementDataProcessor/blob/v1.0.0_spec/spec/Functions/p1StreamPmData/p1MaintainDs/1.0.0/README.md

[openBackhaul]

Question:

As far I have understood the generic word DataStore we are now referencing as Elastic Search.

Answer:

It is assumed that there is a single ElasticSearch instance that holds multiple ElasticSearch indexes.
The ElasticSearch instance is shared by diverse applications, e.g. MWDI and DPMDP.
While MWDI is applying a single ElasticSearch index in that ElasticSearch instance, DPMDP is using three.
These are referred as Replica, Logging and DataStore.
Replica contains the raw data.
Logging contains some internal processing information.
DataStore is holding the result data for a configurable time period.

Question:

Is this the default engine or we have to refer/take in account also others datastore engines?

Answer:

It is a shared ElasticSearch instance.
This can also be seen from the ElasticSearch client configuration in the serviceList:

- http-client:
    application-name: ElasticSearch
    release-number: 1.0.0
    uuid: dpmdp-1-0-0-http-c-es-1-0-0-000
  tcp-client:
    remote-protocol: http
    ip-address: 127.0.0.1
    tcp-port: 3015
    uuid: dpmdp-1-0-0-tcp-c-es-1-0-0-000
  elasticsearch-client:
    - uuid: dpmdp-1-0-0-es-c-es-1-0-0-007
      index-alias: 7
      # MWDI
    - uuid: dpmdp-1-0-0-es-c-es-1-0-0-018
      index-alias: 18
      # MWDI Replica
    - uuid: dpmdp-1-0-0-es-c-es-1-0-0-020
      index-alias: 20
      # Logging
    - uuid: dpmdp-1-0-0-es-c-es-1-0-0-021
      index-alias: 21
      # DataStore