Uploaded image for project: 'Camunda Optimize'
  1. Camunda Optimize
  2. OPT-1228

Import skips entries if they are created the same millisecond other entries were imported

    Details

    • Type: Bug Report
    • Status: Done
    • Priority: L3 - Default
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 2.1.0-alpha2, 2.1.0
    • Component/s: backend
    • Labels:
      None

      Description

      Please have a look at the fetchHistoricActivityInstances method of the ActivityInstanceFetcher class.

      Scenario:

      Problem:

      • If an entity is added to the engine database after the second query is performed, but before the millisecond is over (so it also has the timestamp 1), it is not found, because the next query will only find entities with a timestamp >=2

      Possible solution:

      • Instead of having the non-paginated query after the paginated request, we should have it before, using the non-incremented timestamp of the last found entity
      • Then, we perform the paginated request with the timestamp increased by one ms, but only update the timestamp of the last found entity if this request returns one.

        Activity

        There are no comments yet on this issue.

          People

          • Assignee:
            Unassigned
            Reporter:
            sebastian.stamm Sebastian Stamm
          • Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved: