Exporter can soft pause and resume

[rodrigo-lourenco-lopes]

Description

Exporter can soft pause and resume. This means if the exporter is soft paused, we keep exporting the records without updating the exporter state. upon resuming The exporter state is updated with the position and metadata of the last exported record.

The feature to persist the soft paused state will be implemented in this issue #16642

Related issues

closes #16344

Definition of Done

Not all items need to be done depending on the issue and the pull request.

Code changes:

• The changes are backwards compatibility with previous versions
• If it fixes a bug then PRs are created to backport the fix to the last two minor versions. You can trigger a backport by assigning labels (e.g. backport stable/1.3) to the PR, in case that fails you need to create backports manually.

Testing:

• There are unit/integration tests that verify all acceptance criterias of the issue
• New tests are written to ensure backwards compatibility with further versions
• The behavior is tested manually
• The change has been verified by a QA run
• The impact of the changes is verified by a benchmark

Documentation:

• The documentation is updated (e.g. BPMN reference, configuration, examples, get-started guides, etc.)
• If the PR changes how BPMN processes are validated (e.g. support new BPMN element) then the Camunda modeling team should be informed to adjust the BPMN linting.

Other teams:
If the change impacts another team an issue has been created for this team, explaining what they need to do to support this change.

• Operate
• Tasklist
• Web Modeler
• Desktop Modeler
• Optimize

Please refer to our review guidelines.

[deepthidevaki]

🚀 Awesome. I like the behavior of consecutive calls of pause vs soft-pause, and resume always resumes full exporting, no matter if it was soft paused or hard paused. 👍

❌ I have only one main comment. The exporter director should be able to start with phase soft-paused if it was soft-paused before restart. You can do it in a follow up PR. If so please create an issue for it and link it here for transparency.

Other comments are minor - like improvements to tests and documentation. Please address them in this PR itself.

[deepthidevaki]

🚀

[rodrigo-lourenco-lopes]

/backport

[backport-action]

Successfully created backport PR for stable/8.2:

• [Backport stable/8.2] Exporter can soft pause and resume #17809

[backport-action]

Successfully created backport PR for stable/8.3:

• [Backport stable/8.3] Exporter can soft pause and resume #17810

[backport-action]

Successfully created backport PR for stable/8.4:

• [Backport stable/8.4] Exporter can soft pause and resume #17811

[rodrigo-lourenco-lopes]

/backport

[backport-action]

Git push to origin failed for stable/8.3 with exitcode 1

[backport-action]

Backport failed for stable/8.4, because it was unable to cherry-pick the commit(s).

Please cherry-pick the changes locally and resolve any conflicts.

git fetch origin stable/8.4
git worktree add -d .worktree/backport-16345-to-stable/8.4 origin/stable/8.4
cd .worktree/backport-16345-to-stable/8.4
git switch --create backport-16345-to-stable/8.4
git cherry-pick -x ce0234a6de7451e147a8981262aad60f452c337e 3a123e4e7763ee11565044764288caf74a6db462 adc1dba80868c3cbacb57d59ac5425798223a593

[backport-action]

Backport failed for stable/8.5, because it was unable to cherry-pick the commit(s).

Please cherry-pick the changes locally and resolve any conflicts.

git fetch origin stable/8.5
git worktree add -d .worktree/backport-16345-to-stable/8.5 origin/stable/8.5
cd .worktree/backport-16345-to-stable/8.5
git switch --create backport-16345-to-stable/8.5
git cherry-pick -x ce0234a6de7451e147a8981262aad60f452c337e 3a123e4e7763ee11565044764288caf74a6db462 adc1dba80868c3cbacb57d59ac5425798223a593