-
Task
-
Resolution: Done
-
L3 - Default
-
None
-
None
Part of the implementation for the suggestions API involves retrieving all existing sequence counts that we have stored, and filtering through to find the relevant ones for the given target node. In the case where a lot of event sequences exist, this could be expensive and isn't totally necessary. If we knew beforehand which neighbouring events to look for, we could restrict this lookup to only return sequences that have relevance to the suggestions request
Original PR: https://github.com/camunda/camunda-optimize/pull/1385
ATs:
- Only event sequences that feature neighbouring mappings to the target flow node ID are returned to the Event Service for processing