In Data migrator, Add a mechanism to keep track of skipped entities

[yanavasileva]

User Story (Required on creation)

• As a process engineer, I want to keep track of skipped entities so that I can rerun the migration against them.

Functional Requirements (Required before implementation)

Technical Requirements (Required before implementation)

• Review what the prototype currently does decide if this makes sense, and streamline it for runtime and history.
• Whenever an entity's migration has to be skipped, we insert the C7 ID into the migration mapping table with the C8 key set to null.

Limitations of Scope

Hints

• Time estimate: 5 days
• In Runtime, we currently cannot distinguish between skipped and not yet migrated. This means on retry we would try everything instead of just the skipped instances. Is this a problem? If yes, can we somehow store information to distinguish between skipped and not yet migrated? We have to do it in Runtime like this because starting C8 process instances due to HTTP gRPC request can fail and we cannot react on this.
  • In History, we don’t have this problem since we don’t store all to-be-migrated C7 process instance IDs initially.

Links

• https://github.com/camunda/c7-data-migrator/pull/7

Breakdown

Pull Requests

Preview Give feedback

No tasks being tracked yet.

Dev2QA handover

• Does this ticket need a QA test and the testing goals are not clear from the description? Add a Dev2QA handover comment