-
Notifications
You must be signed in to change notification settings - Fork 93
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
MINFICPP-2243 - In ListenHTTP process incoming request only in onTrigger #1826
base: main
Are you sure you want to change the base?
Conversation
52d14ea
to
4e91dbe
Compare
89d9d1a
to
f5af871
Compare
struct RequestValue { | ||
std::reference_wrapper<core::ProcessSession> session; | ||
std::promise<void> ret; | ||
}; | ||
struct FailureValue { | ||
FailureReason reason; | ||
std::promise<void> ret; | ||
}; | ||
using Request = std::promise<nonstd::expected<RequestValue, FailureValue>>; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why do we have promise in promise here?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
the processor should release all references to the ProcessSession before returning from onTrigger, and since writing the data into the flowfile happens on the Handler's thread, it is not enough for the Handler to wait for the onTrigger's resources (promise1) onTrigger should also wait for the Handler's thread to release these resources (promise2)
There are compilation errors in the CI It was caused by my suggestions, I didn't handle all references |
85adf35
to
2667658
Compare
Co-authored-by: Márton Szász <[email protected]>
Co-authored-by: Márton Szász <[email protected]>
2667658
to
116e244
Compare
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.