MINIFICPP-2771 Use separate state managers in schedule and trigger threads#2157
Open
lordgamez wants to merge 6 commits intoapache:mainfrom
Open
MINIFICPP-2771 Use separate state managers in schedule and trigger threads#2157lordgamez wants to merge 6 commits intoapache:mainfrom
lordgamez wants to merge 6 commits intoapache:mainfrom
Conversation
szaszm
reviewed
Apr 10, 2026
lordgamez
force-pushed
the
MINIFICPP-2771
branch
from
3a197b2 to
305a31f
Compare
martinzink
reviewed
Apr 15, 2026
| void StatefulProcessor::onTrigger(core::ProcessContext&, core::ProcessSession&) { | ||
| void StatefulProcessor::onTrigger(core::ProcessContext& context, core::ProcessSession&) { | ||
| std::lock_guard<std::mutex> lock(mutex_); | ||
| state_manager_ = context.getStateManager(); |
Member
There was a problem hiding this comment.
i know this is test code, but I think it would be clearer if state_manager_ would cease to be a member and only live on the stack during the onschedule and ontrigger
| std::chrono::system_clock::time_point start_push_time_; | ||
| std::vector<std::shared_ptr<core::FlowFile>> batched_flowfiles_; | ||
| core::StateManager* state_manager_; | ||
| core::StateManager* state_manager_ = nullptr; |
Member
There was a problem hiding this comment.
Could we remove this member and only use the state manager in the ontirgger and onschedule as a stack variabl?
Contributor
Author
There was a problem hiding this comment.
This is only used as part of the LogBatch object, but I added a gsl::finally directive to clear it at the end of the onTrigger to be sure in f9e15ed
szaszm
approved these changes
Apr 15, 2026
Member
szaszm
left a comment
szaszm
left a comment
There was a problem hiding this comment.
I'm +1 for this after Martin's comments are resolved. I can see that this design is far from the best, but any better design would require thorough refactoring of core APIs, and I can't suggest a better low impact fix.
fgerlits
reviewed
Apr 16, 2026
lordgamez
force-pushed
the
MINIFICPP-2771
branch
from
b71e562 to
8d8f53c
Compare
fgerlits
reviewed
Apr 17, 2026
fgerlits
approved these changes
Apr 17, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
https://issues.apache.org/jira/browse/MINIFICPP-2771
Thank you for submitting a contribution to Apache NiFi - MiNiFi C++.
In order to streamline the review of the contribution we ask you
to ensure the following steps have been taken:
For all changes:
Is there a JIRA ticket associated with this PR? Is it referenced
in the commit message?
Does your PR title start with MINIFICPP-XXXX where XXXX is the JIRA number you are trying to resolve? Pay particular attention to the hyphen "-" character.
Has your PR been rebased against the latest commit within the target branch (typically main)?
Is your initial contribution a single, squashed commit?
For code changes:
For documentation related changes:
Note:
Please ensure that once the PR is submitted, you check GitHub Actions CI results for build issues and submit an update to your PR as soon as possible.