[
https://issues.apache.org/jira/browse/UNOMI-225?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Serge Huber updated UNOMI-225:
------------------------------
Description:
Currently the backend persistence system only supports ElasticSearch 5.6
We should upgrade it to support ES 7, but this implies:
- splitting types into seperate indices
- switching from the ES Java Transport Client to the ES REST Java High Level
Client (this might require some custom JSON requests for features such as the
cluster request or system info that don't exist in the REST High-level client)
was:
Currently the backend persistence system only supports ElasticSearch 5.6
We should upgrade it to support ES 7, but this implies:
- splitting types into seperate indices
- switching from the ES Java Transport Client to the ES Java High Level Client
- (optional) improving at the same time ways that data is stored to make it
easier to sync between multiple ES cluster, for example to synchronize profiles
and events in multiple data centers and centralize them.
> Upgrade backend to ElasticSearch 7
> ----------------------------------
>
> Key: UNOMI-225
> URL: https://issues.apache.org/jira/browse/UNOMI-225
> Project: Apache Unomi
> Issue Type: Bug
> Components: core
> Affects Versions: 1.4.0
> Reporter: Serge Huber
> Priority: Major
> Fix For: 1.5.0
>
>
> Currently the backend persistence system only supports ElasticSearch 5.6
> We should upgrade it to support ES 7, but this implies:
> - splitting types into seperate indices
> - switching from the ES Java Transport Client to the ES REST Java High Level
> Client (this might require some custom JSON requests for features such as the
> cluster request or system info that don't exist in the REST High-level client)
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
