Reuse transaction

[Zelldon]

Description

Instead of relying of the implementation that it resets the transaction on rollback or commit, we renew the transaction via #beginTransaction .

Related issues

closes #2397

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/0.25) 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.)
• New content is added to the release announcement

[npepinpe]

Can you elaborate on the choice to add a new interface instead of making renew (or refresh or whatever) be part of the Transaction behaviour itself?

[Zelldon]

Not sure whether I get your question right. Is the question why the interface is not part of the Transaction or why I not have added a reference to the db, such that it can reuse the transaction? Maybe for clarity to begin a transaction you need to have access to the database.

[npepinpe]

Ah, I thought Transaction was from our code base 🙈 Nevermind 😅

[npepinpe]

🎉

[Zelldon]

bors r+

[zeebe-bors]

Build succeeded:

• continuous-integration/jenkins/branch