Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Diverge stream processor packages from engine #10454

Closed
wants to merge 15 commits into from
Closed

Conversation

Zelldon
Copy link
Member

@Zelldon Zelldon commented Sep 22, 2022

Description

Iterate over the engine and stream processor packages, renamed and reorganized them. This should make it easier to make a split soon. I realized during doing this some smaller blockers which we need to tackler before completely separating the modules.

See #10130

Blocked by #10440

Related issues

See #10130

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

Please refer to our review guidelines.

Create the key generator in the StreamProcessor, since the key is part
of the Record metadata, which is know by the StreamProcessor and needs
to be reset during replay.

The keygenerator is part of the RecordProcessorContext and corresponding
API.
The keygenerator is no longer created inside the ZeebeState, it is
passed into the CTOR from outside. Coming from the
RecordProcessorContext, created by the streamprocessor.
@Zelldon
Copy link
Member Author

Zelldon commented Oct 14, 2022

I will keep the branch, but close the PR

@Zelldon Zelldon closed this Oct 14, 2022
@Zelldon Zelldon deleted the zell-split-modules branch March 28, 2024 15:51
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

1 participant