-
Type:
Task
-
Resolution: Done
-
Priority:
L3 - Default
-
Affects Version/s: 3.0.0
-
Component/s: backend
-
100
Context:
Going forward from the beta status reached with OPT-2719 we need to iterate on the overall event based import setup.
Things to consider are:
- consider making publish update state, index management & definition import to be controlled on a per process basis rather than having a service doing that cross-process
- reconsider the usage of a shared vs dedicated import job executor for all active event process instance imports
AT:
- rather than having a static import scheduler interval configured we want to use a continuous running import thread (just like the engine import)
- adopt EventProcessInstanceImportMediator to fully implement the Import architecture(split it up into mediator, indexhandler, make it extend timeStampBasedMediator)
- rather then reusing the engine import config of the ElasticsearchImportJobExecutor we should have a dedicated configuration for the event import
- in the indexManager replace the Phaser used to track usages with an atomic int
This is the controller panel for Smart Panels app
1.
|
Replace Phaser with AtomicInt in EventProcessInstanceIndexManager |
|
Done | Unassigned |
2.
|
Extend Import Mediator Interface to reflect async import job status |
|
Done | Unassigned |
3.
|
Refactor EventProcessInstanceImportMediator to fully implement the Import architecture |
|
Done | Unassigned |
4.
|
Keep track of correlatedEventIds in event process flow node instances |
|
Done | Unassigned |
5.
|
Dedicated event process import configuration |
|
Done | Unassigned |
6.
|
Do not reimport identical entitiesLastTimestamp batches |
|
Done | Unassigned |
7.
|
Remove scheduling of event based import but run it continously |
|
Done | Unassigned |