-
Type: Improvement
-
Status: Open
-
Priority: Minor
-
Resolution: Unresolved
-
Affects Version/s: None
-
Fix Version/s: QualifiedToSchedule
-
Component/s: Core
-
Tags:
-
Story Points:5
Today there is a JPA implementation but as noted in NXP-18017 this impl is to be avoided.
We need a simple and reliable sequencer based on SQL.
The goal is to use by default the implementation based on the repository backend,
so we can avoid using elasticsearch for this (Elasticsearch should not be considered as a storage/source of truth).
There is already a MongoDBUIDSequencer we need the same for SQL database.
- is related to
-
NXP-18017 Fix JPA UIDSequencer
- Open