-
Type: New Feature
-
Status: Resolved
-
Priority: Minor
-
Resolution: Fixed
-
Affects Version/s: None
-
Fix Version/s: 6.0
-
Component/s: Elasticsearch
When a sequence number is needed and must be consistent across a cluster, the standard solution is to use a SQL Database.
We already have such a service in Nuxeo, but the implementation is far from ideal.
Audit Service requires to attach a sequence ID to the events :
- this sequence Id was previously generate by the DB in the JPA implementation
- we rely on this eventId for some part of the code (like Drive)
When moving the Audit Backend to ES, we need a way to maintain a cluster safe sequence id.
The idea is to implement a sequence generator service on top of ES using the approach described in :
- is required by
-
NXP-15087 Implement Audit service interface backend on top of elasticsearch
- Resolved